Re: Using __sync_* builtins within libgcc code

2008-06-11 Thread Luke Dalessandro
Paolo Carlini wrote: Luke Dalessandro wrote: I'm making some modifications to exception handling inside of unwind-dw2-fde.c that I'd like to use __sync_bool_compare_and_swap for, unfortunately I can't seem to figure out how to correctly use builtins in the context of libgcc. I've tried a bun

Re: Using __sync_* builtins within libgcc code

2008-06-10 Thread Ross Smith
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. I've long been of the opinion that -march=native should

Re: Using __sync_* builtins within libgcc code

2008-06-10 Thread H.J. Lu
On Tue, Jun 10, 2008 at 7:42 AM, Joseph S. Myers <[EMAIL PROTECTED]> wrote: > 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 -

Re: Using __sync_* builtins within libgcc code

2008-06-10 Thread Andrew Haley
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).

Re: Using __sync_* builtins within libgcc code

2008-06-10 Thread Joseph S. Myers
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

Re: Using __sync_* builtins within libgcc code

2008-06-10 Thread H.J. Lu
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 a

Re: Using __sync_* builtins within libgcc code

2008-06-10 Thread Paolo Carlini
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. Paolo.

Re: Using __sync_* builtins within libgcc code

2008-06-10 Thread Joseph S. Myers
On Tue, 10 Jun 2008, Paolo Carlini wrote: > Luke Dalessandro wrote: > > I'm making some modifications to exception handling inside of > > unwind-dw2-fde.c that I'd like to use __sync_bool_compare_and_swap for, > > unfortunately I can't seem to figure out how to correctly use builtins in > > the co

Re: Using __sync_* builtins within libgcc code

2008-06-10 Thread Uros Bizjak
Hello! > I'm making some modifications to exception handling inside of > unwind-dw2-fde.c that I'd like to use __sync_bool_compare_and_swap for, > unfortunately I can't seem to figure out how to > correctly use builtins in the context of libgcc. > I've tried a bunch of different things, but I c

Re: Using __sync_* builtins within libgcc code

2008-06-09 Thread Paolo Carlini
Luke Dalessandro wrote: I'm making some modifications to exception handling inside of unwind-dw2-fde.c that I'd like to use __sync_bool_compare_and_swap for, unfortunately I can't seem to figure out how to correctly use builtins in the context of libgcc. I've tried a bunch of different things