http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46018
--- Comment #8 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2010-10-18 15:37:04 UTC --- On Sun, 17 Oct 2010, ahaas at airmail dot net wrote: > Running 'git bisect' but interpreting a failed build as 'good' and a > successful > build as 'bad' leads to this commit which restored the build: > > 7332acfcfbd1a9c70674c62419096022f72bd201 is the first bad commit > commit 7332acfcfbd1a9c70674c62419096022f72bd201 > Author: jsm28 <js...@138bc75d-0d04-0410-961f-82ee72b054a4> > Date: Sat Oct 16 12:12:24 2010 +0000 > > * config/arm/arm.c (arm_option_optimization): Set > flag_section_anchors to 1 not 2. > * config/i386/i386.c (ix86_option_override_internal): Check > global_options_set.x_flag_zee and > global_options_set.x_flag_omit_frame_pointer. > (ix86_option_optimization): Don't set flag_omit_frame_pointer and > flag_zee to 2. > * config/i386/sol2-10.h (SUBTARGET_OVERRIDE_OPTIONS): Check > global_options_set.x_flag_omit_frame_pointer. This certainly wasn't meant to change the behavior of the compiler at all. I'll test a patch to restore the original intended behavior (and so the build failure for this target).
