public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "Bernhard.Rosenkranzer at linaro dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/52520] New: trunk: internal compiler error: in predict_insn, at predict.c:477 Date: Wed, 07 Mar 2012 11:12:00 -0000 [thread overview] Message-ID: <bug-52520-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52520 Bug #: 52520 Summary: trunk: internal compiler error: in predict_insn, at predict.c:477 Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end AssignedTo: unassigned@gcc.gnu.org ReportedBy: Bernhard.Rosenkranzer@linaro.org Created attachment 26850 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=26850 Preprocessed source (not yet reduced) Trying to build bionic with current trunk (but not 4.6 or 4.7) at -O2 or higher results in: [bero@localhost android]$ /tmp/android-toolchain-eabi/bin/arm-linux-androideabi-gcc -o out/target/product/pandaboard/obj/SHARED_LIBRARIES/libc_intermediates/bionic/dlmalloc.o -c dlmalloc.i -O2 bionic/libc/bionic/dlmalloc.c: In function 'sys_trim.constprop.6': bionic/libc/bionic/dlmalloc.c:3830:1: internal compiler error: in commit_one_edge_insertion, at cfgrtl.c:1631 Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions.
next reply other threads:[~2012-03-07 11:12 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-07 11:12 Bernhard.Rosenkranzer at linaro dot org [this message] 2012-03-07 11:42 ` [Bug middle-end/52520] " steven at gcc dot gnu.org 2012-03-07 11:57 ` steven at gcc dot gnu.org 2012-03-07 12:24 ` Bernhard.Rosenkranzer at linaro dot org 2012-03-07 12:27 ` Bernhard.Rosenkranzer at linaro dot org 2012-03-07 13:07 ` steven at gcc dot gnu.org 2012-03-07 16:58 ` Bernhard.Rosenkranzer at linaro dot 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-52520-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).