This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Using __sync_* builtins within libgcc code

From: "H.J. Lu" <hjl dot tools at gmail dot com>
To: Paolo Carlini <paolo dot carlini at oracle dot com>
Cc: "Joseph S. Myers" <joseph at codesourcery dot com>, Luke Dalessandro <luked at cs dot rochester dot edu>, gcc at gcc dot gnu dot org
Date: Tue, 10 Jun 2008 07:38:50 -0700
Subject: Re: Using __sync_* builtins within libgcc code
References: <484DF34C.5040005@cs.rochester.edu> <484E21D5.4020201@oracle.com> <Pine.LNX.4.64.0806101155290.19304@digraph.polyomino.org.uk> <484E7325.5050205@oracle.com>

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.


H.J.

Follow-Ups:
- Re: Using __sync_* builtins within libgcc code
  - From: Joseph S. Myers
- Re: Using __sync_* builtins within libgcc code
  - From: Andrew Haley

References:
- Using __sync_* builtins within libgcc code
  - From: Luke Dalessandro
- Re: Using __sync_* builtins within libgcc code
  - From: Paolo Carlini
- Re: Using __sync_* builtins within libgcc code
  - From: Joseph S. Myers
- Re: Using __sync_* builtins within libgcc code
  - From: Paolo Carlini

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]