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/53086] New: [4.8 Regression] 416.gamess in SPEC CPU 2006 miscompiled Date: Mon, 23 Apr 2012 13:58:00 -0000 [thread overview] Message-ID: <bug-53086-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53086 Bug #: 53086 Summary: [4.8 Regression] 416.gamess in SPEC CPU 2006 miscompiled 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, rguenth@gcc.gnu.org Depends on: 53073 +++ This bug was initially created as a clone of Bug #53073 +++ On Linux/x86-64, revision 186600 compiles 416.gamess in SPEC CPU 2006 into infinite loop. Revision 186566 is OK.
next reply other threads:[~2012-04-23 13:58 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-23 13:58 hjl.tools at gmail dot com [this message] 2012-04-23 15:06 ` [Bug middle-end/53086] " rguenth at gcc dot gnu.org 2012-04-23 15:09 ` rguenth at gcc dot gnu.org 2012-04-23 15:13 ` [Bug fortran/53086] " rguenth at gcc dot gnu.org 2012-04-23 16:10 ` kargl at gcc dot gnu.org 2012-04-23 16:30 ` hjl.tools at gmail dot com 2012-04-24 7:58 ` rguenth at gcc dot gnu.org 2012-04-24 8:39 ` pinskia at gcc dot gnu.org 2012-04-24 9:16 ` pinskia at gcc dot gnu.org 2012-04-24 9:18 ` pinskia at gcc dot gnu.org 2012-04-24 9:30 ` rguenth at gcc dot gnu.org 2012-04-24 14:50 ` sgk at troutmask dot apl.washington.edu 2012-04-25 6:47 ` burnus at gcc dot gnu.org 2012-04-25 13:34 ` sgk at troutmask dot apl.washington.edu 2012-04-25 13:58 ` rguenth at gcc dot gnu.org 2013-02-01 16:10 ` pthaugen at gcc dot gnu.org 2015-05-14 10:04 ` dominiq at lps dot ens.fr
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-53086-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).