public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/62301] [5 Regression] PowerPC bootstrap broken since r214654
Date: Fri, 29 Aug 2014 15:00:00 -0000 [thread overview]
Message-ID: <bug-62301-4-oAfGivHxpz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-62301-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62301
rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2014-08-29
CC| |rsandifo at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |rsandifo at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #5 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
(In reply to Bill Schmidt from comment #4)
> Unfortunately that was not sufficient -- same SEGVs are still occurring.
Sorry, it was a really dumb typo. Instead of:
if (GET_CODE (y) == LABEL_REF && LABEL_P (y) && XEXP (y, 0) == x)
it should be:
if (GET_CODE (y) == LABEL_REF && LABEL_P (x) && XEXP (y, 0) == x)
I confirmed that that is enough to get identical expmed.c code before
and after the patch, am testing a full bootstrap now.
next prev parent reply other threads:[~2014-08-29 15:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 3:12 [Bug bootstrap/62301] New: " wschmidt at gcc dot gnu.org
2014-08-29 4:19 ` [Bug bootstrap/62301] " wschmidt at gcc dot gnu.org
2014-08-29 8:56 ` [Bug bootstrap/62301] [5 Regression] " rguenth at gcc dot gnu.org
2014-08-29 13:20 ` wschmidt at gcc dot gnu.org
2014-08-29 13:42 ` wschmidt at gcc dot gnu.org
2014-08-29 14:11 ` wschmidt at gcc dot gnu.org
2014-08-29 15:00 ` rsandifo at gcc dot gnu.org [this message]
2014-08-29 15:45 ` wschmidt at gcc dot gnu.org
2014-08-29 15:51 ` rsandifo at gcc dot gnu.org
2014-08-29 15:55 ` rsandifo at gcc dot gnu.org
2014-08-29 16:09 ` wschmidt at gcc dot gnu.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-62301-4-oAfGivHxpz@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).