Andrew Kolchoogin <[EMAIL PROTECTED]> writes:
> On Fri, Aug 02, 2002 at 12:39:55AM -0700, David O'Brien wrote:
> > The rest of the GCC using world can use -O2 on their code. We are the
> > only ones that have so much trouble with it. It is probably due to our
> > bugs, not GCC's.
> 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.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message