public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/65087] New: [5 Regression] r220742 causes: ICE:
Date: Tue, 17 Feb 2015 08:23:00 -0000	[thread overview]
Message-ID: <bug-65087-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65087

            Bug ID: 65087
           Summary: [5 Regression] r220742 causes: ICE:
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: ipa
          Assignee: unassigned at gcc dot gnu.org
          Reporter: trippels at gcc dot gnu.org
                CC: hubicka at gcc dot gnu.org, jakub at gcc dot gnu.org,
                    jgreenhalgh at gcc dot gnu.org

Building Firefox with LTO on gcc112 fails during final libxul link
since r220742:

lto1: internal compiler error: in ipcp_verify_propagated_values, at
ipa-cp.c:1057
0x10d1202f ipcp_verify_propagated_values()
        ../../gcc/gcc/ipa-cp.c:1057
0x10d1415b ipcp_propagate_stage
        ../../gcc/gcc/ipa-cp.c:2758
0x10d1415b ipcp_driver
        ../../gcc/gcc/ipa-cp.c:4407
0x10d1415b execute
        ../../gcc/gcc/ipa-cp.c:4502
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
lto-wrapper: fatal error: ../../../gcc_test/usr/local/bin/c++ returned 1 exit
status

A similar issue was fixed a few days ago: PR64978


             reply	other threads:[~2015-02-17  8:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-17  8:23 trippels at gcc dot gnu.org [this message]
2015-02-17  8:46 ` [Bug ipa/65087] [5 Regression] r220742 causes: ICE: in ipcp_verify_propagated_values, at ipa-cp.c:1057 jakub at gcc dot gnu.org
2015-02-17  8:47 ` jakub at gcc dot gnu.org
2015-02-17  9:03 ` trippels at gcc dot gnu.org
2015-02-17  9:05 ` jakub at gcc dot gnu.org
2015-02-17 10:22 ` rguenth at gcc dot gnu.org
2015-02-18 11:37 ` jakub at gcc dot gnu.org
2015-02-18 13:46 ` trippels at gcc dot gnu.org
2015-02-27 12:28 ` trippels at gcc dot gnu.org
2015-02-27 14:14 ` trippels at gcc dot gnu.org
2015-03-02 16:05 ` marxin at gcc dot gnu.org
2015-03-03  9:22 ` marxin 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-65087-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: 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).