From: Andre Vehreschild <vehre@gmx.de>
To: Paul Richard Thomas <paul.richard.thomas@gmail.com>
Cc: VandeVondele Joost <joost.vandevondele@mat.ethz.ch>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] PR67518 and PR53852 -- add testcase.
Date: Sun, 08 Nov 2015 17:18:00 -0000 [thread overview]
Message-ID: <20151108181802.4a09e310@vepi2> (raw)
In-Reply-To: <CAGkQGiJKfBx_xQM6Vasg9eEVBd_BTgv6fH0r8YezTXp1O_HsYA@mail.gmail.com>
Hi Paul,
I fell for the same issue. You need a more recent isl library then
0.14.2. I installed 0.12.something when I started gfortran hacking and
didn't upgrade since.
You can get the ISL lib from:
ftp://gcc.gnu.org/pub/gcc/infrastructure/
or from your distribution (Fedora 21 is shipping 0.14.3, which is
sufficient to run the test.)
Regards,
Andre
On Sun, 8 Nov 2015 18:02:15 +0100
Paul Richard Thomas <paul.richard.thomas@gmail.com> wrote:
> Dear Joost,
>
> These cause regressions on my tree:
> f951: sorry, unimplemented: Graphite loop optimizations cannot be used
> (ISL is not available)(-fgraphite, -fgraphite-identity, -floop-block,
> -floop-interchange, -floop-strip-mine, -floop-parallelize-all,
> -floop-unroll-and-jam, and -ftree-loop-linear)
>
> I suppose that I can deal with it. However, is there some way to
> detect the presence of ISL? I'll try and figure out some dejagnu-ery
> to pass the tests if this message comes up.
>
> Cheers
>
> Paul
>
> On 6 November 2015 at 10:45, VandeVondele Joost
> <joost.vandevondele@mat.ethz.ch> wrote:
> > Thanks Paul. I believe PR53852 won't be fixed on 4.9/5 as it seems to depend on the recent graphite cleanup work and recent isl. As such I'll commit to trunk only.
>
>
>
--
Andre Vehreschild * Email: vehre ad gmx dot de
next prev parent reply other threads:[~2015-11-08 17:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 18:22 VandeVondele Joost
2015-11-06 7:04 ` VandeVondele Joost
2015-11-06 9:25 ` Paul Richard Thomas
2015-11-06 9:45 ` VandeVondele Joost
2015-11-08 17:02 ` Paul Richard Thomas
2015-11-08 17:18 ` Andre Vehreschild [this message]
2015-11-08 19:05 ` VandeVondele Joost
2015-11-08 19:14 ` VandeVondele Joost
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=20151108181802.4a09e310@vepi2 \
--to=vehre@gmx.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=joost.vandevondele@mat.ethz.ch \
--cc=paul.richard.thomas@gmail.com \
/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).