public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/65414] [5 Regression] ICE while building libgcc after stage 2, bootstrap failure on aarch64-linux-gnu
Date: Mon, 16 Mar 2015 00:10:00 -0000 [thread overview]
Message-ID: <bug-65414-4-S1RXyqbYc9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65414-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65414
--- Comment #12 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #11)
> I am almost 100% sure it was caused by
> e2a16b9122d238b8877640b5f6ef1599e195fae0 (revision 221372). I am checking
> if reverting this patch from the current upstream will not crash.
yes reverting that patch fixes the bootstrap for me.
next prev parent reply other threads:[~2015-03-16 0:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 23:28 [Bug target/65414] New: [5 Regression] ICE, bootstrap failure on aarch64-linux-gnu in stage2 doko at gcc dot gnu.org
2015-03-13 9:20 ` [Bug target/65414] [5 Regression] ICE while building libgcc after stage 2, bootstrap failure on aarch64-linux-gnu rguenth at gcc dot gnu.org
2015-03-13 11:47 ` doko at gcc dot gnu.org
2015-03-13 13:21 ` ramana at gcc dot gnu.org
2015-03-14 10:25 ` jakub at gcc dot gnu.org
2015-03-14 15:28 ` doko at gcc dot gnu.org
2015-03-14 15:59 ` doko at gcc dot gnu.org
2015-03-14 20:27 ` pinskia at gcc dot gnu.org
2015-03-14 20:42 ` pinskia at gcc dot gnu.org
2015-03-15 10:06 ` pinskia at gcc dot gnu.org
2015-03-15 10:40 ` pinskia at gcc dot gnu.org
2015-03-15 11:26 ` pinskia at gcc dot gnu.org
2015-03-15 23:13 ` [Bug middle-end/65414] " pinskia at gcc dot gnu.org
2015-03-16 0:10 ` pinskia at gcc dot gnu.org [this message]
2015-03-16 9:43 ` vries at gcc dot gnu.org
2015-03-16 9:48 ` vries at gcc dot gnu.org
2015-03-16 11:01 ` vries at gcc dot gnu.org
2015-03-16 14:09 ` jakub at gcc dot gnu.org
2015-03-16 17:39 ` 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=bug-65414-4-S1RXyqbYc9@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).