From: Sebastian Pop <sebpop@gmail.com>
To: Jeff Law <law@redhat.com>
Cc: Mike Frysinger <vapier@gentoo.org>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] gcc: fix building w/isl-0.15
Date: Fri, 24 Jul 2015 22:08:00 -0000 [thread overview]
Message-ID: <20150724215313.GB12889@f1.c.bardezibar.internal> (raw)
In-Reply-To: <55B12B94.9070402@redhat.com>
Jeff Law wrote:
> On 07/21/2015 02:32 PM, Sebastian Pop wrote:
> >
> >Could somebody with access to sourceware.org upload a tar.bz2 of the required
> >version of isl from http://isl.gforge.inria.fr/isl-0.15.tar.bz2?
> >
> >Also, once that is done, I will commit the following patch updating the
> >documentation.
> I've put isl-0.15.tar.bz2 into the ftp directory.
>
> However, I don't think we've changed the required version of ISL for
> gcc. If we were changing the required version, then I wouldn't have
> bothered to verify that the trunk still works with 0.13 (and the
> patch itself would have been simpler).
>
> What I think we've done is merely allow the use of a newer ISL,
> possibly changing the recommended version, but not the base required
> version.
Right, I have misunderstood the patch, as I though that the configure bits would
check for the existence of a file only distributed in isl-0.15. Updated patch.
Ok to commit to trunk?
Thanks,
Sebastian
From e9e2685bcffbfa3a9129a1e10574dee907fa4377 Mon Sep 17 00:00:00 2001
From: Sebastian Pop <sebpop@gmail.com>
Date: Tue, 21 Jul 2015 20:26:36 +0000
Subject: [PATCH] update doc for supported isl versions
---
gcc/doc/install.texi | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
index 212008a..40c7e6e 100644
--- a/gcc/doc/install.texi
+++ b/gcc/doc/install.texi
@@ -383,11 +383,11 @@ installed but it is not in your default library search path, the
@option{--with-mpc} configure option should be used. See also
@option{--with-mpc-lib} and @option{--with-mpc-include}.
-@item ISL Library version 0.14 (or 0.12.2)
+@item ISL Library version 0.15, 0.14, 0.13, or 0.12.2
Necessary to build GCC with the Graphite loop optimizations.
-It can be downloaded from @uref{ftp://gcc.gnu.org/pub/gcc/infrastructure/}
-as @file{isl-0.12.2.tar.bz2}. If an ISL source distribution is found
+It can be downloaded from @uref{ftp://gcc.gnu.org/pub/gcc/infrastructure/}.
+If an ISL source distribution is found
in a subdirectory of your GCC sources named @file{isl}, it will be
built together with GCC. Alternatively, the @option{--with-isl} configure
option should be used if ISL is not installed in your default library
--
1.7.10.4
next prev parent reply other threads:[~2015-07-24 21:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 14:45 Mike Frysinger
2015-07-17 11:36 ` [PATCH] gcc/: Fix building with isl-0.15.0; includes Bernhard Reutner-Fischer
2015-07-21 18:42 ` [PATCH] gcc: fix building w/isl-0.15 Jeff Law
2015-07-21 21:11 ` Sebastian Pop
2015-07-21 21:45 ` Mike Stump
2015-07-23 18:11 ` Jeff Law
2015-07-24 22:08 ` Sebastian Pop [this message]
2015-07-24 22:42 ` Jeff Law
2015-07-22 0:40 ` Mike Frysinger
2015-07-19 21:28 james harvey
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=20150724215313.GB12889@f1.c.bardezibar.internal \
--to=sebpop@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=vapier@gentoo.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).