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 middle-end/53062] New: [4.8 Regression] 445.gobmk in SPEC CPU 2006 failed to build Date: Sat, 21 Apr 2012 14:20:00 -0000 [thread overview] Message-ID: <bug-53062-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53062 Bug #: 53062 Summary: [4.8 Regression] 445.gobmk in SPEC CPU 2006 failed to build Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end AssignedTo: unassigned@gcc.gnu.org ReportedBy: hjl.tools@gmail.com CC: areg.melikadamyan@gmail.com On Linux/x86-64, revision 186591 gave gcc -c -o engine/matchpat.o -DSPEC_CPU -DNDEBUG -DHAVE_CONFIG_H -I. -I.. -I../include -I./include -O3 -funroll-loops -ffast-math -fwhole-program -flto=jobserver -fuse-linker-plugin -DSPEC_CPU_LP64 engine/matchpat.c engine/matchpat.c: In function 'dfa_prepare_for_match': engine/matchpat.c:504:1: internal compiler error: Segmentation fault dfa_prepare_for_match(int color) ^ Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. Revision 186507 is OK.
next reply other threads:[~2012-04-21 14:20 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-21 14:20 hjl.tools at gmail dot com [this message] 2012-04-21 17:19 ` [Bug middle-end/53062] " hjl.tools at gmail dot com 2012-04-21 18:12 ` hjl.tools at gmail dot com 2012-08-16 11:06 ` rguenth at gcc dot gnu.org 2012-09-07 11:24 ` rguenth at gcc dot gnu.org 2012-09-19 12:20 ` rguenth 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-53062-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).