From: Randolph Chung <randolph@tausq.org>
To: Guy Martin <gmsoft@gentoo.org>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] gcc and -march=2.0 flag bug
Date: Mon, 12 May 2003 14:58:37 -0700 [thread overview]
Message-ID: <20030512215837.GN4509@tausq.org> (raw)
In-Reply-To: <200305122351.57449.gmsoft@gentoo.org>
> I had some problems with gcc. When I set the CFLAGS/CXXFLAGS -march=2.0, most
> of the applications builded are b0rked. This occured on many stations. Using
> -march=1.1 works well.
How are they "b0rked"? Can you be a bit more precise?
> Is this a 'feature' of unimplemented 64bit userspace or is this a bug ?
>
> In case of a bug, what do you need to debug it.
We compile pa20 32-bit kernels (e.g. for c3k) using 32-bit and
-march=2.0. seems to work. Do you have a test case for what you think
is broken? -march2.0 is really orthogonal to 64-bit userspace.
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
next prev parent reply other threads:[~2003-05-12 21:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 21:51 [parisc-linux] gcc and -march=2.0 flag bug Guy Martin
2003-05-12 21:58 ` Randolph Chung [this message]
2003-05-12 22:59 ` John David Anglin
-- strict thread matches above, loose matches on Subject: below --
2003-05-13 16:53 Guy Martin
2003-05-13 17:53 ` John David Anglin
2003-05-13 18:03 ` Guy Martin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030512215837.GN4509@tausq.org \
--to=randolph@tausq.org \
--cc=gmsoft@gentoo.org \
--cc=parisc-linux@lists.parisc-linux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox