Description of problem: Invoking a command "gcc -ON filename.c" (for N >= 256) causes an internal compiler error. See steps to reproduce for more details. Version-Release number of selected component (if applicable): $ gcc --version gcc (GCC) 4.4.1 20090725 (Red Hat 4.4.1-2) Copyright (C) 2009 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. How reproducible: Always. Steps to Reproduce: $ touch a.c $ gcc -O256 a.c cc1: internal compiler error: in cl_optimization_save, at options.c:5594 Please submit a full bug report, with preprocessed source if appropriate. See <http://bugzilla.redhat.com/bugzilla> for instructions. Actual results: See above. Expected results: The compiler should not get killed. Additional info:
Why are you doing it, when only -O{,0,1,2,3,s} mean anything?
(In reply to comment #1) > Why are you doing it, when only -O{,0,1,2,3,s} mean anything? My friend found this only by chance. There was no specific intention. At least, GCC shouldn't cause the internal error in this case. GCC should accept (or reject) it gracefully.
http://gcc.gnu.org/ml/gcc-patches/2009-11/msg01290.html
Fixed in gcc-4.4.2-12.fc12.