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/53144] New: [4.8 Regression] gcc.c-torture/execute/vector-compare-1.c Date: Fri, 27 Apr 2012 16:41:00 -0000 [thread overview] Message-ID: <bug-53144-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53144 Bug #: 53144 Summary: [4.8 Regression] gcc.c-torture/execute/vector-compare-1.c 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: bonzini@gnu.org On Linux/x86-64, revision 186905: http://gcc.gnu.org/ml/gcc-cvs/2012-04/msg00858.html caused: WARNING: program timed out. FAIL: gcc.c-torture/execute/vector-compare-1.c compilation, -O3 -fomit-frame-pointer WARNING: program timed out. FAIL: gcc.c-torture/execute/vector-compare-1.c compilation, -O3 -fomit-frame-pointer -funroll -loops WARNING: program timed out. FAIL: gcc.c-torture/execute/vector-compare-1.c compilation, -O3 -fomit-frame-pointer -funroll -all-loops -finline-functions WARNING: program timed out. FAIL: gcc.c-torture/execute/vector-compare-1.c compilation, -O3 -g
next reply other threads:[~2012-04-27 16:41 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-27 16:41 hjl.tools at gmail dot com [this message] 2012-04-28 0:27 ` [Bug middle-end/53144] " hp at gcc dot gnu.org 2012-04-28 6:20 ` bonzini at gnu dot org 2012-04-28 15:47 ` [Bug middle-end/53144] [4.7/4.8 Regression] PPRE infinite loop bonzini at gnu dot org 2012-04-28 15:53 ` hjl.tools at gmail dot com 2012-04-28 18:59 ` hjl.tools at gmail dot com 2012-05-02 10:44 ` rguenth at gcc dot gnu.org 2012-05-02 12:18 ` rguenth at gcc dot gnu.org 2012-05-02 14:08 ` rguenth at gcc dot gnu.org 2012-05-03 8:38 ` rguenth at gcc dot gnu.org 2012-05-03 8:50 ` rguenth at gcc dot gnu.org 2012-05-03 8:51 ` 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-53144-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).