From: Andreas Simbuerger <simbuerg@googlemail.com>
To: Jack Howarth <howarth@bromo.med.uc.edu>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
gcc-graphite@googlegroups.com, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 0/3] Configure support for official CLooG versions.
Date: Fri, 13 Aug 2010 16:09:00 -0000 [thread overview]
Message-ID: <4C656E43.3070907@googlemail.com> (raw)
In-Reply-To: <20100813143529.GB32225@bromo.med.uc.edu>
On 08/13/2010 04:35 PM, Jack Howarth wrote:
> Andreas,
> Is it possible that cloog.org's cloog 0.15 release
> could be modified to require ppl 0.11 or later? This
> might be useful way to handle the transition of both
> ppl from 0.10.x to 0.11 and cloog-ppl to cloog.org.
> Since it seems unlikely that gcc 4.5.x will be fixed
> to build against cloog.org and cloog-ppl can't build
> against ppl-0.11, this locks gcc 4.5.x and earlier
> in at cloog-ppl 0.15.9/ppl 0.10.2. If gcc 4.6 is
> configured to only build against cloog.org (and not
> cloog-ppl), we won't have to worry about which ppl
> release gcc 4.6 is built against (since it must
> be ppl 0.11 or later to satisfy cloog 0.15).
> Jack
I have to discuss this on the next graphite call.
As far is i remember Sebastian did not want to
extend CLooG-PPL any further, except critical bugs.
I will have a look.
Andreas
next prev parent reply other threads:[~2010-08-13 16:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cloog1>
2010-08-11 18:30 ` [PATCH 2/3] Fix include order to avoid failed compilation on CLOOG_ORG Andreas Simbürger
2010-08-11 21:01 ` Sebastian Pop
2010-08-11 18:30 ` [PATCH 1/3] Add necessary accessors for CloogMatrix (CLOOG_ORG) Andreas Simbürger
2010-08-11 20:54 ` Sebastian Pop
2010-08-11 18:30 ` [PATCH 0/3] Configure support for official CLooG versions Andreas Simbürger
2010-08-11 19:02 ` Sebastian Pop
2010-08-11 19:18 ` Jack Howarth
2010-08-11 19:27 ` Andreas Simbuerger
2010-08-11 21:55 ` Matthias Klose
[not found] ` <2876_1281553691_4C62F51B_2876_2281_1_20100811190756.GB18599@bromo.med.uc.edu>
2010-08-11 19:23 ` Tobias Grosser
2010-08-12 6:14 ` Roberto Bagnara
2010-08-21 9:16 ` Gerald Pfeifer
2010-08-23 16:51 ` Richard Guenther
2010-08-11 19:08 ` Jack Howarth
2010-08-11 20:37 ` Andreas Simbuerger
2010-08-11 22:13 ` Joseph S. Myers
2010-08-11 22:34 ` Andreas Simbuerger
2010-08-11 23:39 ` Joseph S. Myers
2010-08-12 8:05 ` Andreas Simbuerger
2010-08-12 10:01 ` Joseph S. Myers
2010-08-12 20:25 ` Andreas Simbuerger
2010-08-13 15:01 ` Jack Howarth
2010-08-13 16:09 ` Andreas Simbuerger [this message]
2010-08-13 19:25 ` Sebastian Pop
2010-08-12 13:39 ` Jack Howarth
2010-08-12 18:52 ` Andreas Simbuerger
2010-08-12 19:43 ` Jack Howarth
2010-08-13 16:09 ` Andreas Simbuerger
2010-08-13 16:16 ` Jack Howarth
2010-08-13 16:31 ` Andreas Simbuerger
2010-08-11 18:45 ` [PATCH 3/3] Support official CLooG.org versions Andreas Simbürger
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=4C656E43.3070907@googlemail.com \
--to=simbuerg@googlemail.com \
--cc=gcc-graphite@googlegroups.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=howarth@bromo.med.uc.edu \
--cc=joseph@codesourcery.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).