From: "Joseph S. Myers" <joseph@codesourcery.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Paolo Carlini <paolo.carlini@oracle.com>,
Luke Dalessandro <luked@cs.rochester.edu>,
gcc@gcc.gnu.org
Subject: Re: Using __sync_* builtins within libgcc code
Date: Tue, 10 Jun 2008 14:43:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0806101440170.20379@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20080610143850.GA3997@lucon.org>
On Tue, 10 Jun 2008, H.J. Lu wrote:
> On Tue, Jun 10, 2008 at 02:27:17PM +0200, Paolo Carlini wrote:
> > Joseph S. Myers wrote:
> >> I hold that it is a bug that i686-* tools default to -march=i386 instead
> >> of -march=i686 (whereas e.g. sparcv9-* tools default to -mcpu=sparcv9, and
> >> -mcpu means -march for SPARC).
> > Seconded.
> >
>
> What arch should be used for -m32 on x86-64? Personally, I think
> it should be at least i686, if not SSE2.
-march=x86-64, I'd say, if you're configuring as x86_64-* (so assuming
those 32-bit features present on all 64-bit processors). Obviously,
subject to override from --with-arch-32 or --with-arch.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2008-06-10 14:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 3:22 Luke Dalessandro
2008-06-10 6:40 ` Paolo Carlini
2008-06-10 12:01 ` Joseph S. Myers
2008-06-10 14:22 ` Paolo Carlini
2008-06-10 14:39 ` H.J. Lu
2008-06-10 14:43 ` Joseph S. Myers [this message]
2008-06-10 15:37 ` H.J. Lu
2008-06-10 15:36 ` Andrew Haley
2008-06-10 16:34 ` Ross Smith
2008-06-11 12:35 ` Luke Dalessandro
2008-06-10 11:45 Uros Bizjak
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=Pine.LNX.4.64.0806101440170.20379@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=luked@cs.rochester.edu \
--cc=paolo.carlini@oracle.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).