Date: Sun, 4 Aug 2002 20:01:10 +1000 (EST) From: Bruce Evans <bde@zeta.org.au> To: Mike Barcroft <mike@FreeBSD.ORG> Cc: Andrew Kolchoogin <andrew@snark.rinet.ru>, "David O'Brien" <obrien@FreeBSD.ORG>, <current@FreeBSD.ORG> Subject: Re: Comments on Release Building for -current Message-ID: <20020804195905.O1075-100000@gamplex.bde.org> In-Reply-To: <20020803123249.B70372@espresso.q9media.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 3 Aug 2002, Mike Barcroft wrote: > Andrew Kolchoogin <andrew@snark.rinet.ru> 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020804195905.O1075-100000>