public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/65603] New: [5 Regression] lto1: internal compiler error: in as_a, at is-a.h:192
Date: Fri, 27 Mar 2015 14:07:00 -0000	[thread overview]
Message-ID: <bug-65603-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 65603
           Summary: [5 Regression] lto1: internal compiler error: in as_a,
                    at is-a.h:192
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: lto
          Assignee: unassigned at gcc dot gnu.org
          Reporter: hjl.tools at gmail dot com

On Linux/x86-64, r221721 gave

gcc -c -o obstack.o   -DSPEC_CPU2000_LP64 -Dalloca=_alloca        -O3
-funroll-loops -ffast-math -fwhole-program -flto=jobserver -fuse-linker-plugin 
obstack.c
gcc     -O3 -funroll-loops -ffast-math -fwhole-program -flto=jobserver
-fuse-linker-plugin -DSPEC_CPU2000_LP64 c-parse.o c-lang.o c-lex.o c-pragma.o
c-decl.o c-typeck.o c-convert.o c-aux-info.o c-common.o c-iterate.o toplev.o
version.o tree.o print-tree.o stor-layout.o fold-const.o function.o stmt.o
expr.o calls.o expmed.o explow.o optabs.o varasm.o rtl.o print-rtl.o rtlanal.o
emit-rtl.o real.o dbxout.o sdbout.o dwarfout.o xcoffout.o integrate.o jump.o
cse.o loop.o unroll.o flow.o stupid.o combine.o regclass.o local-alloc.o
global.o reload.o reload1.o caller-save.o insn-peep.o reorg.o sched.o final.o
recog.o reg-stack.o insn-opinit.o insn-recog.o insn-extract.o insn-output.o
insn-emit.o insn-attrtab.o m88k.o getpwd.o convert.o bc-emit.o bc-optab.o
obstack.o   -lm  -o cc1
In function 'set_float_handler.constprop':
lto1: internal compiler error: in as_a, at is-a.h:192
0x6856d8 gcall* as_a<gcall*, gimple_statement_base>(gimple_statement_base*)
    ../../src-trunk/gcc/is-a.h:192
0x6856d8 cgraph_update_edges_for_call_stmt_node
    ../../src-trunk/gcc/cgraph.c:1524
0x685a19 cgraph_update_edges_for_call_stmt(gimple_statement_base*, tree_node*,
gimple_statement_base*)
    ../../src-trunk/gcc/cgraph.c:1588
0xa96570 fold_marked_statements
    ../../src-trunk/gcc/tree-inline.c:4843
0xaa39c4 tree_function_versioning(tree_node*, tree_node*, vec<ipa_replace_map*,
va_gc, vl_embed>*, bool, bitmap_head*, bool, bitmap_head*, basic_block_def*)
    ../../src-trunk/gcc/tree-inline.c:5813
0x692c13 cgraph_materialize_clone
    ../../src-trunk/gcc/cgraphclones.c:1056
0x692c13 symbol_table::materialize_all_clones()
    ../../src-trunk/gcc/cgraphclones.c:1153
0x68d969 symbol_table::compile()
    ../../src-trunk/gcc/cgraphunit.c:2326
0x602f84 lto_main()
    ../../src-trunk/gcc/lto/lto.c:3496
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.
make[4]: *** [/tmp/ccBkg1Up.ltrans3.ltrans.o] Error 1


             reply	other threads:[~2015-03-27 13:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-27 14:07 hjl.tools at gmail dot com [this message]
2015-03-27 14:10 ` [Bug lto/65603] " hjl.tools at gmail dot com
2015-03-27 14:22 ` jakub at gcc dot gnu.org
2015-03-27 14:46 ` trippels 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-65603-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).