public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ahaas at airmail dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/46018] [4.6 Regression] Bootstrap fails on i386-pc-solaris2.10
Date: Sun, 17 Oct 2010 15:45:00 -0000	[thread overview]
Message-ID: <20101017154500.OCV7bCk3lb0zBEgKxJ-NarydzljPMaLINPslXw91WJg@z> (raw)
In-Reply-To: <bug-46018-4@http.gcc.gnu.org/bugzilla/>

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 <jsm28@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/trunk@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.


  parent reply	other threads:[~2010-10-17 15:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-14 15:30 [Bug bootstrap/46018] New: " ahaas at airmail dot net
2010-10-14 15:34 ` [Bug bootstrap/46018] [4.6 Regression] " pinskia at gcc dot gnu.org
2010-10-14 15:57 ` hjl.tools at gmail dot com
2010-10-14 15:58 ` hjl.tools at gmail dot com
2010-10-14 20:11 ` ahaas at airmail dot net
2010-10-14 20:14 ` ahaas at airmail dot net
2010-10-16 19:16 ` ahaas at airmail dot net
2010-10-17 15:45 ` ahaas at airmail dot net [this message]
2010-10-18 15:04 ` ahaas at airmail dot net
2010-10-18 15:37 ` joseph at codesourcery dot com
2010-10-18 21:28 ` ahaas at airmail dot net
2010-10-21 18:42 ` hjl.tools at gmail dot com
2010-10-26 14:40 ` ahaas at airmail dot net
2010-10-30 13:59 ` hjl.tools at gmail dot com
2010-10-30 17:55 ` ahaas at airmail dot net
2010-11-03 13:11 ` ro at gcc dot gnu.org
2010-11-03 13:13 ` ro at gcc dot gnu.org
2010-11-03 17:09 ` hjl.tools at gmail dot com
2010-11-03 18:32 ` pinskia at gcc dot gnu.org
2010-11-04 12:52 ` ahaas at airmail dot net
2010-11-05 13:08 ` hjl.tools at gmail dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20101017154500.OCV7bCk3lb0zBEgKxJ-NarydzljPMaLINPslXw91WJg@z \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).