Piotr Wyderski wrote:
> Andrew Pinski wrote:
>
>> i386 did not have atomic locks at all but 486 and above does.
>
> Thanks, now it is obvious to me. So how should
> I configure my GCC-trunk build? It seems that
> --with-cpu is not enough:
You need to look closer at the definition of -mcpu, -mt
Andrew Pinski wrote:
> i386 did not have atomic locks at all but 486 and above does.
Thanks, now it is obvious to me. So how should
I configure my GCC-trunk build? It seems that
--with-cpu is not enough:
$ gcc -v
Using built-in specs.
Target: i686-pc-cygwin
Configured with: ../configure --prefix
On Thu, May 28, 2009 at 4:00 PM, Piotr Wyderski
wrote:
> is not, as Cygwin does not use glibc. Its underlying
> processor architecture, however, supports the fullest
> set of atomic primitives, so is there really a need to
> make it glibc-dependent? If I enforce the macro
> definition from the com
