public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at bromo dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/64145] New: gcc.dg/graphite/isl-codegen-loop-dumping.c UNRESOLVED with isl 0.14
Date: Mon, 01 Dec 2014 21:57:00 -0000 [thread overview]
Message-ID: <bug-64145-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64145
Bug ID: 64145
Summary: gcc.dg/graphite/isl-codegen-loop-dumping.c UNRESOLVED
with isl 0.14
Product: gcc
Version: 5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: howarth at bromo dot med.uc.edu
The gcc.dg/graphite/isl-codegen-loop-dumping.c testcase appears as UNRESOLVED
when gcc trunk is built against isl 0.14. The test suite log shows...
Executing on host: /sw/src/fink.build/gcc50-5.0.0-1000/darwin_objdir/gcc/xgcc
-B/sw/src/fink.build/gcc50-5.0.0-1000/darwin_objdir/gcc/
/sw/src/fink.build/gcc50-5.0.0-1000/gcc-5-20141201/gcc/testsuite/gcc.dg/graphite/isl-codegen-loop-dumping.c
-fno-diagnostics-show-caret -fdiagnostics-color=never -O2
-fdump-tree-graphite-all -S -m32 -o isl-codegen-loop-dumping.s (timeout =
300)
spawn /sw/src/fink.build/gcc50-5.0.0-1000/darwin_objdir/gcc/xgcc
-B/sw/src/fink.build/gcc50-5.0.0-1000/darwin_objdir/gcc/
/sw/src/fink.build/gcc50-5.0.0-1000/gcc-5-20141201/gcc/testsuite/gcc.dg/graphite/isl-codegen-loop-dumping.c
-fno-diagnostics-show-caret -fdiagnostics-color=never -O2
-fdump-tree-graphite-all -S -m32 -o isl-codegen-loop-dumping.s^M
PASS: gcc.dg/graphite/isl-codegen-loop-dumping.c (test for excess errors)
gcc.dg/graphite/isl-codegen-loop-dumping.c: dump file does not exist
UNRESOLVED: gcc.dg/graphite/isl-codegen-loop-dumping.c scan-tree-dump-times
graphite "ISL AST generated by ISL: \nfor \\(int c1 = 0; c1 < n - 1; c1 \\+=
1\\)\n for \\(int c3 = 0; c3 < n; c3 \\+= 1\\)\n S_4\\(c1, c3\\);" 1
with -fdump-tree-graphite-all apparently not creating any dump files.
next reply other threads:[~2014-12-01 21:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 21:57 howarth at bromo dot med.uc.edu [this message]
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 ` [Bug testsuite/64145] [5 Regression] gcc.dg/graphite/isl-codegen-loop-dumping.c UNRESOLVED after r217315 dominiq at lps dot ens.fr
2014-12-04 8:46 ` 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@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).