On Thu, Dec 20, 2012 at 05:46:33PM +0000, Christian Weisgerber wrote: > Edd Barrett <vex...@gmail.com> wrote: > > > Subject: Cranking the optimiser on selected ports? > > No. > > > Now, I know we don't usually like to turn the optimiser up past -O2 for > > fear of compiler bugs making crappy code, however, the code gcc has made > > in this case for my amd64 machine seems to be ok. > > Optimizer levels other than -O2 are essentially untested. They may > reveal compiler bugs. (We discovered a lot of instances of -O1 in > the ports tree because gcc3 on alpha frequently blew up on it.) > They may reveal broken source code (-fstrict-aliasing). They may > produce broken code. This will vary by architecture. The produced > code is typically larger, which may be a pessimization if it overflows > a cache level. > > > I spoke to Jasper on icb about the possibility of making exceptions. > > I'm afraid this will lead to people asking for exceptions for more > and more ports. > > > What do people think? Are any of the options acceptable? > > I don't like it. FWIW.
same as naddy. Specifically because -O2 is the only optimization level that's really tested...
