After a request from Paul de Vrieze on the -dev mailing list for me to file a bug concerning the commented examples in the skeleton make.conf that ships with x86 stageballs. Quoted from my first mail in the thread: "I'd just like to know why -O3 is the default (commented) -O in make.conf, even for x86 stage tarballs (I don't really know about the stageballs on other architectures). Although the usefulness / harm of this flag has been discussed to death, on the vast majority of x86 /desktop/ machines I don't really think this flag is that suitable, and I know many agree. The reason I ask is because many people who didn't really change the default flags beyond setting -march have come on #gentoo or on the forums unsatisfied with performance of Gentoo, and there are also several packages that still won't compile with -O3. As an example for x86, wouldn't -O2 be more suitable? My personal viewpoint is that if you want to set -O3 on x86, go ahead. But if you do, you should know why you want to do it, and what affects it will have. Many beginners who haven't really got their heads around CFLAGS will possibly read somewhere that -O3 gives the most optimisation and be sold there and then." The thread was started on 01/25/04 at 12:18 GMT, title "Default -O CFLAG in make.conf. Thanks. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Silly me, It was avenj that told me to file a bug no Paul de Vrieze.
This should no longer be a problem.
