Hi Sébastien,
since glibc 2.6-2, Debian's glibc and vanilla glibc are different WRT this 
bug. The bug is fixed with Debian's glibc, but not vanilla glibc. It's not 
clear whether this is a gcc or glibc bug. Is it OK if we consider this report 
to be only about an incompatibility between Debian's glibc and gcc, and thus 
fixed, or do you consider the problem a gcc bug which isn't fixed?

Reply via email to