public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/45150]  New: [4.6 Regression] bootstrap debug-compare fail
Date: Sat, 31 Jul 2010 13:20:00 -0000	[thread overview]
Message-ID: <bug-45150-19002@http.gcc.gnu.org/bugzilla/> (raw)

i686-apple-darwin9 bootstrap is broken since r162678 (with an ICE reported for
other targets as well).
Since this was fixed (at r162697), it has unmasked another fail which is still
present at 162778.

unfortunately, the other bootstrap bug prevents narrowing this down more...
however;

This is a compare-debug fail of cfgexpand.o.
Looking at the .s files (to be attached) there seem to be instruction ordering
differences.

this bug is _not_ present in powerpc-apple-darwin9 or x86_64-apple-darwin10.


-- 
           Summary: [4.6 Regression] bootstrap debug-compare fail
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: blocker
          Priority: P3
         Component: middle-end
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: iains at gcc dot gnu dot org
GCC target triplet: i686-apple-darwin9


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45150


             reply	other threads:[~2010-07-31 13:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-31 13:20 iains at gcc dot gnu dot org [this message]
2010-07-31 13:22 ` [Bug middle-end/45150] " iains at gcc dot gnu dot org
2010-07-31 13:26 ` iains at gcc dot gnu dot org
2010-07-31 18:48 ` iains at gcc dot gnu dot org
2010-08-04 15:01 ` danglin at gcc dot gnu dot org
2010-08-04 15:16 ` bernds at gcc dot gnu dot org

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=bug-45150-19002@http.gcc.gnu.org/bugzilla/ \
    --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).