public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <rguenther@suse.de>
To: gcc-patches@gcc.gnu.org
Cc: Jakub Jelinek <jakub@redhat.com>
Subject: [PATCH] Allow new ISL/CLooG versions
Date: Mon, 14 Jan 2013 14:29:00 -0000	[thread overview]
Message-ID: <alpine.LNX.2.00.1301141525590.6889@zhemvz.fhfr.qr> (raw)


This makes us accept the CLooG 0.18.0 and ISL 0.11.1 combo.

It's probably not the best stage to move the version checks to
gcc/ where we can rely on built in-tree ISL/CLooG, so this avoids
it with the caveat that in-tree CLooG 0.18.0 will fail the
version check (they no longer ship built version.h but only
version.h.in).

I verified all GRAPHITE tests pass with 0.18.0/0.11.1.

Ok for trunk?

Or do people prefer to move CLooG/ISL checks to gcc/ configure
time to fix the in-tree use of 0.18.0 and also do version checks
of in-tree ISL at all (they don't have a version.h).

Thanks,
Richard.

2013-01-14  Richard Biener  <rguenther@suse.de>

	* configure.ac (cloog/isl): Also allow ISL 0.11.x and CLooG 0.18.0.
	* configure: Re-generate.

Index: configure.ac
===================================================================
--- configure.ac	(revision 195144)
+++ configure.ac	(working copy)
@@ -1606,8 +1606,11 @@ if test "x$with_isl" != "xno" &&
   dnl Provide configure switches and initialize islinc & isllibs
   dnl with user input.
   ISL_INIT_FLAGS
-  dnl The minimal version of ISL required for Graphite.
+  dnl The versions of ISL that work for Graphite
   ISL_CHECK_VERSION(0,10)
+  if test "${gcc_cv_isl}" = no ; then
+    ISL_CHECK_VERSION(0,11)
+  fi
   dnl Only execute fail-action, if ISL has been requested.
   ISL_IF_FAILED([
     AC_MSG_ERROR([Unable to find a usable ISL.  See config.log for details.])])
@@ -1617,11 +1620,11 @@ if test "x$with_isl" != "xno" &&
     dnl Provide configure switches and initialize clooginc & clooglibs
     dnl with user input.
     CLOOG_INIT_FLAGS
-    dnl The minimal version of CLooG required for Graphite.
-    dnl
-    dnl If we use CLooG-Legacy, the provided version information is
-    dnl ignored.
+    dnl The versions of CLooG that work for Graphite.
     CLOOG_CHECK_VERSION(0,17,0)
+    if test "${gcc_cv_cloog}" = no ; then
+      CLOOG_CHECK_VERSION(0,18,0)
+    fi
 
     dnl Only execute fail-action, if CLooG has been requested.
     CLOOG_IF_FAILED([

             reply	other threads:[~2013-01-14 14:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-14 14:29 Richard Biener [this message]
2013-01-14 15:44 ` Tobias Grosser
2013-01-14 16:03   ` Jack Howarth
2013-01-14 16:29     ` Jack Howarth
2013-01-14 18:20       ` Richard Biener
2013-01-14 20:04         ` Jack Howarth
2013-01-20 10:15 ` Eric Botcazou
2013-01-20 13:27   ` Richard Biener
2013-01-14 19:27 Dominique Dhumieres
2013-01-14 20:20 ` Jack Howarth
2013-01-14 20:29   ` Dominique Dhumieres
2013-01-14 20:45     ` Jack Howarth
2013-01-15  9:24   ` Richard Biener
2013-01-15 10:06     ` Richard Biener
2013-01-15 12:58       ` Jakub Jelinek
2013-01-15 14:07       ` Jack Howarth
2013-01-16  9:31         ` Richard Biener
2013-01-16  9:36           ` Richard Biener
2013-01-14 20:18 Dominique Dhumieres

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=alpine.LNX.2.00.1301141525590.6889@zhemvz.fhfr.qr \
    --to=rguenther@suse.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.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).