http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46018
--- Comment #6 from Art Haas <ahaas at airmail dot net> 2010-10-17 15:45:40 UTC
---
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.
* config/rs6000/rs6000.c (rs6000_option_init_struct): Set
opts->x_flag_section_anchors to 1 not 2.
* config/sh/sh.c (sh_option_optimization): Don't set
flag_schedule_insns to 2.
(sh_option_override): Check
global_options_set.x_flag_schedule_insns.
* opts.c (finish_options): Check opts_set->x_flag_section_anchors.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/tr...@165539
138bc75d-0d04-0410-961f-82ee72b054a4
:040000 040000 4d93fdb436ce6c956250256c221c663f7d085bb0
0dd0b04692b88501a315407dd58cfaae228d1c89 M gcc
I'll leave it to those much more savvy regarding GCC internals to figure out
what caused the initial build failure and why things started working again.
