public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/52939] New: ice in gimple_get_virt_method_for_binfo with -O3 Date: Wed, 11 Apr 2012 21:07:00 -0000 [thread overview] Message-ID: <bug-52939-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52939 Bug #: 52939 Summary: ice in gimple_get_virt_method_for_binfo with -O3 Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned@gcc.gnu.org ReportedBy: dcb314@hotmail.com Created attachment 27137 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27137 gzipped C++ source code I just tried to compile the package openfst-1.3.1-1 on gcc-4.8 trunk dated 20120411 on an AMD x86_64 box. The compiler said determinize.cc: At global scope: determinize.cc:38:1: internal compiler error: in gimple_get_virt_method_for_binfo, at gimple-fold.c:3093 Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. Preprocessed source code attached. Flag -O3 required.
next reply other threads:[~2012-04-11 21:07 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-11 21:07 dcb314 at hotmail dot com [this message] 2012-04-12 9:31 ` [Bug middle-end/52939] [4.7/4.8 Regression] " rguenth at gcc dot gnu.org 2012-04-12 15:11 ` jamborm at gcc dot gnu.org 2012-04-12 17:05 ` jamborm at gcc dot gnu.org 2012-04-13 9:59 ` rguenth at gcc dot gnu.org 2012-04-13 13:18 ` rguenth at gcc dot gnu.org 2012-04-13 13:56 ` jamborm at gcc dot gnu.org 2012-04-13 17:57 ` jamborm at gcc dot gnu.org 2012-04-16 10:02 ` jamborm at gcc dot gnu.org 2012-04-16 10:11 ` jamborm at gcc dot gnu.org 2012-08-22 23:53 ` blelbach at cct dot lsu.edu 2012-08-23 9:31 ` jamborm 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-52939-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).