Keith M Wesolowski wrote: > On Fri, Mar 17, 2006 at 11:53:30PM +0100, Roland Mainz wrote: > > > Note that when building ON with gcc, we use -fno-builtin. > > > > Why ? I understand this is usefull for debugging - but it kills some > > interesting opportunities for optimisation... ;-( > > While I'm not the one who implemented this, I'm all but certain it's > to prevent gcc from sticking big fat functions like memcpy inline, > and/or using less-efficient generic functions when the > platform-optimized libc function should be used instead.
Is there no way to use gcc's builtin functions except those which should be handled by the platform-optimized libc ? Using -fno-builtin is like hunting ducks with a Abrahams tank... > Have you actually benchmarked with builtin/no-builtin? Yes, but I did that with Mozilla (and not ON which was not available for the public at that time) where it was a (minor) win in several subsystems including libjpeg, NSPR, libpng, necko and NSS. Other parts like layout/content are difficult to measure so Mozilla as whole application wasn't benchmarked but it was thought that it's still worth to turn -xbuiltin=%all for the whole build. ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) [EMAIL PROTECTED] \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;) _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
