public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/64145] [5 Regression] gcc.dg/graphite/isl-codegen-loop-dumping.c UNRESOLVED after r217315.
Date: Tue, 02 Dec 2014 13:22:00 -0000 [thread overview]
Message-ID: <bug-64145-4-H8OEb42AMV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64145-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64145
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |romangareev at gcc dot gnu.org
Component|other |testsuite
Summary|gcc.dg/graphite/isl-codegen |[5 Regression]
|-loop-dumping.c UNRESOLVED |gcc.dg/graphite/isl-codegen
|with isl 0.14 |-loop-dumping.c UNRESOLVED
| |after r217315.
--- Comment #4 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
AFAICT this has nothing to do with isl 0.14, but is due to a typo in r217315
where " -fgraphite-identity -fgraphite-code-generator=isl" has been deleted
instead of only " -fgraphite-code-generator=isl".
next prev parent reply other threads:[~2014-12-02 13:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 21:57 [Bug other/64145] New: gcc.dg/graphite/isl-codegen-loop-dumping.c UNRESOLVED with isl 0.14 howarth at bromo dot med.uc.edu
2014-12-01 22:07 ` [Bug other/64145] " dominiq at lps dot ens.fr
2014-12-02 0:54 ` howarth at bromo dot med.uc.edu
2014-12-02 1:08 ` howarth at bromo dot med.uc.edu
2014-12-02 13:22 ` dominiq at lps dot ens.fr [this message]
2014-12-04 8:46 ` [Bug testsuite/64145] [5 Regression] gcc.dg/graphite/isl-codegen-loop-dumping.c UNRESOLVED after r217315 fxcoudert at gcc dot gnu.org
2015-01-09 11:20 ` rguenth at gcc dot gnu.org
2015-02-16 15:02 ` mpolacek at gcc dot gnu.org
2015-02-25 9:17 ` law at redhat dot com
2015-02-25 14:49 ` law at redhat dot com
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-64145-4-H8OEb42AMV@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: link
Be 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).