On Sat, 3 Aug 2002, Mike Barcroft wrote: > Andrew Kolchoogin <[EMAIL PROTECTED]> writes: > > ... > > sorry, but some time ago I read here that gcc -O2 breaks our printf() in > > libc. I haven't find any assembler code in /usr/src/lib/libc/stdio/vfprintf.c, > > as such, if some C compiler can't handle VALID and STANDARDS-COMPLIANT C code, > > this compiler is broken. Isn't it? > > > > Indeed, all of FreeBSD users could help to catch such a bug in gcc optimizer > > code. :) > > If someone could find the small segment of code where the optimizer > screws up, and write a small program to demonstrate the problem, we > would have a good chance of it getting fixed.
Er, someone (Dan Lukes) has already done this. See PR 40209. I'm sorry I haven't found time to look at it in detail. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
