Ways to stop gcc from doing stuff we don't want

Mordae mordae at anilinux.org
Wed Sep 17 22:56:49 PDT 2008


On Thursday 18 September 2008 05:45:54 Robert Connolly wrote:
> While upgrading my desktop I added a couple new things to gcc's specs:
> *cc1_options:
> %{O3:%eDon't use -O3} %{march=i486:;:%{march=*:%eDon't set -march}}
> This causes -O3, and -march={anything but i486}, to stop gcc, because I
> don't want to use buggy gcc optimizations.

Hi, no -O3 is nice, but i486? It made like 15% on Xeon... that's a lot.

Can you point me to some info on these optimization bugs?



More information about the hlfs-dev mailing list