Messages in this thread | | | Subject | Re: what libc+compiler is in use for development? | Date | Sun, 18 Jul 1999 20:38:53 -0400 | From | Horst von Brand <> |
| |
Artur Skawina <skawina@geocities.com> said: > Horst von Brand wrote: > > be a kernel error (the current -fno-strict-aliasing flag is there to work > > around illegal code in the kernel (very pervasive and hard to find/fix, > > unfortunately), not a gcc bug; BTW this inhibits useful optimizations).
> i keep hearing this (ie how bad -fno-strict-aliasing is). instead of a > comment here's an asm diff (34k) between a kernel compiled (1) with that > option, and (2) w/o -fno-strict-aliasing. judge for yourself... > > http://www.geocities.com/SiliconValley/Heights/6494/sw/difffnsa.txt.gz > > [kernel 2.3.5+lots of patches, gcc2.95-19990716, CFLAGS as in 2.3.11, > configured for 686, +/- std config (ide+scsi+most of networking)] > > (it doesn't show anything wrt correctness; just what gcc2.95's > "strict aliasing" means for code generation)
The "correctness" bothers me a bit: A kernel without -fno-strict-aliasing doesn't boot here. Might be a blessing ;-)
Could you give a summary of your findings? -- Horst von Brand vonbrand@sleipnir.valparaiso.cl Casilla 9G, Viña del Mar, Chile +56 32 672616
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |