public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/62301] New: PowerPC bootstrap broken since r214654 Date: Fri, 29 Aug 2014 03:12:00 -0000 [thread overview] Message-ID: <bug-62301-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62301 Bug ID: 62301 Summary: PowerPC bootstrap broken since r214654 Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: wschmidt at gcc dot gnu.org CC: rdsandiford at googlemail dot com Host: powerpc64le-unknown-linux-gnu Target: powerpc64le-unknown-linux-gnu Build: powerpc64le-unknown-linux-gnu Bootstrap is failing in stage 2 for powerpc64le-unknown-linux-gnu (and likely in powerpc64-unknown-linux-gnu as well, though I have not yet confirmed this). I've bisected the start of the failure to r214654: 2014-08-28 Richard Sandiford <rdsandiford@googlemail.com> * rtl.h (get_pool_constant, rtx_referenced_p): Replace rtx parameters with const_rtx parameters. * varasm.c (get_pool_constant): Likewise. * rtlanal.c (rtx_referenced_p_1): Delete. (rtx_referenced_p): Use FOR_EACH_SUBRTX instead of for_each_rtx. Assert that the rtx we're looking for is nonnull. Allow searches for constant pool SYMBOL_REFs. Many compiles fail while building libgcc, all segfaulting: /home/wschmidt/gcc/gcc-mainline-base/libgcc/libgcc2.c: In function '__ashlti3': /home/wschmidt/gcc/gcc-mainline-base/libgcc/libgcc2.c:454:1: internal compiler error: Segmentation fault } ^ xgcc: internal compiler error: Segmentation fault (program cc1) Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. I'll try to get more information in the morning.
next reply other threads:[~2014-08-29 3:12 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-08-29 3:12 wschmidt at gcc dot gnu.org [this message] 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 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@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: linkBe 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).