Re: libgcc/sync.c vs. cgraph alias tracking

2013-10-09 Thread Jakub Jelinek
On Wed, Oct 09, 2013 at 10:56:33AM +0100, Richard Sandiford wrote: > gcc/testsuite/ > * gcc.target/i386/asm-rename-1.c: New file. > > Index: gcc/testsuite/gcc.target/i386/asm-rename-1.c > === > --- /dev/null 2013-10-09 10:21:20.

Re: libgcc/sync.c vs. cgraph alias tracking

2013-10-09 Thread Richard Sandiford
Jakub Jelinek writes: > On Wed, Oct 09, 2013 at 10:59:35AM +0200, Jan Hubicka wrote: >> I see, the previous implementation tricked the one-declaration rule by >> introducing two names. What made the difference is that the second name >> is expanded as builtin... >> >> So you don't have __bulitin_

Re: libgcc/sync.c vs. cgraph alias tracking

2013-10-09 Thread Jakub Jelinek
On Wed, Oct 09, 2013 at 10:59:35AM +0200, Jan Hubicka wrote: > I see, the previous implementation tricked the one-declaration rule by > introducing two names. What made the difference is that the second name > is expanded as builtin... > > So you don't have __bulitin_sync_synchronize() at hand th

Re: libgcc/sync.c vs. cgraph alias tracking

2013-10-09 Thread Jan Hubicka
> Jan Hubicka writes: > >> MIPS16 code can't do atomic operations directly, so it calls into > >> out-of-line > >> versions that are compiled as -mno-mips16. These out-of-line versions use > >> the same open-coded implementation as you'd get in normal -mno-mips16 code. > > > > Hmm, and I assume

Re: libgcc/sync.c vs. cgraph alias tracking

2013-10-08 Thread Richard Sandiford
Jan Hubicka writes: >> MIPS16 code can't do atomic operations directly, so it calls into out-of-line >> versions that are compiled as -mno-mips16. These out-of-line versions use >> the same open-coded implementation as you'd get in normal -mno-mips16 code. > > Hmm, and I assume you don't want to

Re: libgcc/sync.c vs. cgraph alias tracking

2013-10-08 Thread Jan Hubicka
> MIPS16 code can't do atomic operations directly, so it calls into out-of-line > versions that are compiled as -mno-mips16. These out-of-line versions use > the same open-coded implementation as you'd get in normal -mno-mips16 code. Hmm, and I assume you don't want to use target attribute for th