Re: [bug #18217] glibc: `__libc_once'

does not make sense ___ Bug-hurd mailing list Bug-hurd@gnu.org http://lists.gnu.org/mailman/listinfo/bug-hurd

Re: [bug #18217] glibc: `__libc_once'

Thomas Schwinge wrote: Follow-up Comment #2, bug #18217 (project hurd): Roland: ``Uli abused the macros. To support the use he wants, __libc_once should be revamped in all its implementations to return a value or have a variant that does (value says whether fn just ran).'' Is there any r

Re: gcc-4.1 with fastmath

show x/i $pc or similar, maybe disas $pc at the fault. Presumably the fxrstor insn. Check the mxcsr value. ___ Bug-hurd mailing list Bug-hurd@gnu.org http://lists.gnu.org/mailman/listinfo/bug-hurd

gcc-4.1 with fastmath

Heya gang, I was able to build gcc-4.1 with a crtfastmath.o by changing config.gcc to the following: i[34567]86-*-gnu*) tmake_file="${tmake_file} i386/t-crtfm" ;; But when running the attached test code compiled with --fast-math, I get the following: Starting program: /devel/

[bug #18218] glibc: `MSG_NOSIGNAL'

Follow-up Comment #1, bug #18218 (project hurd): Roland: ``best would be to implement MSG_NOSIGNAL in sendmsg.'' ___ Reply to this item at: ___ Messag

[bug #18217] glibc: `__libc_once'

Follow-up Comment #2, bug #18217 (project hurd): Roland: ``Uli abused the macros. To support the use he wants, __libc_once should be revamped in all its implementations to return a value or have a variant that does (value says whether fn just ran).'' ___