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/49662] New: [4.7 Regression] FAIL: gcc.dg/graphite/interchange-XX.c Date: Wed, 06 Jul 2011 18:25:00 -0000 [thread overview] Message-ID: <bug-49662-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49662 Summary: [4.7 Regression] FAIL: gcc.dg/graphite/interchange-XX.c Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end AssignedTo: unassigned@gcc.gnu.org ReportedBy: hjl.tools@gmail.com CC: rguenth@gcc.gnu.org On Linux/x86, revision 175916: http://gcc.gnu.org/ml/gcc-cvs/2011-07/msg00181.html caused: FAIL: gcc.dg/graphite/interchange-14.c scan-tree-dump-times graphite "will be interchanged" 1 FAIL: gcc.dg/graphite/interchange-15.c scan-tree-dump-times graphite "will be interchanged" 1 FAIL: gcc.dg/graphite/interchange-mvt.c scan-tree-dump-times graphite "will be interchanged" 1
next reply other threads:[~2011-07-06 18:25 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-07-06 18:25 hjl.tools at gmail dot com [this message] 2011-07-07 9:26 ` [Bug middle-end/49662] " rguenth at gcc dot gnu.org 2011-07-07 22:41 ` spop at gcc dot gnu.org 2011-07-08 8:43 ` rguenth at gcc dot gnu.org 2011-07-08 8:44 ` [Bug tree-optimization/49662] [4.7 Regression] XFAIL: gcc.dg/graphite/interchange-XX.c, PRE confuses loop interchange rguenth at gcc dot gnu.org 2011-09-30 9:41 ` ro at gcc dot gnu.org 2011-09-30 9:59 ` rguenther at suse dot de 2011-10-10 11:53 ` 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-49662-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).