From: Jack Howarth <howarth@bromo.med.uc.edu>
To: Andreas Simbuerger <simbuerg@googlemail.com>
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: Thu, 12 Aug 2010 13:39:00 -0000 [thread overview]
Message-ID: <20100812133917.GA24267@bromo.med.uc.edu> (raw)
In-Reply-To: <4C632351.7050905@googlemail.com>
On Thu, Aug 12, 2010 at 12:25:21AM +0200, Andreas Simbuerger wrote:
> On 08/11/2010 11:55 PM, Joseph S. Myers wrote:
> > On Wed, 11 Aug 2010, Andreas Simbürger wrote:
> >
> >> this patch series adds configure support for upstream CLooG versions.
> >> The official CLooG is able to use three different backends during
> >> code generation. An ISL backend, a PPL backend and a PolyLib backend.
> > Does ISL involve another library that would be linked against instead of
> > PPL, that needs installing separately from CLooG? If so, this patch
> > series appears incomplete, as it doesn't include any addition of
> > information about ISL to install.texi, or --with-isl etc. options
> > analogous to the --with-ppl options, or configure code that adds -lisl or
> > similar (as opposed to -lcloog-isl). All these things are needed for
> > making GCC link with a new host-side library. In addition it will be
> > necessary to check the portability of ISL to different hosts, similarly to
> > how people tested PPL on various hosts before the original Graphite merge,
> > including cases such as building it with cross compilers.
> >
> The Integer Set Library (ISL) is used within CLooG's backend instead
> of the PPL (Another backend using the PolyLib is available too).
> The official CLooG version provides it's own ISL bundle which
> get's installed alongside CLooG itself. The ISL is exclusively used by
> CLooG for now.
Andreas,
Are there any benchmarks comparing the performance of graphite with
cloog-isl, cloog-polylib and cloog-ppl? In particular, how do the three
compare in effectiveness of properly finding loops and are there large
differences in the time they require to process the data? I had assumed
that cloog-ppl built against ppl-0.11 would be the preferred option
for graphite in gcc 4.6.
Jack
>
> This patch series only prepare GCC for the transition from the CLooG-PPL
> fork,
> maintained by Graphite to the CLooG versions maintained by upstream.
>
> Regards,
> Andreas
>
next prev parent reply other threads:[~2010-08-12 13:39 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 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
2010-08-13 19:25 ` Sebastian Pop
2010-08-12 13:39 ` Jack Howarth [this message]
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: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: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=20100812133917.GA24267@bromo.med.uc.edu \
--to=howarth@bromo.med.uc.edu \
--cc=gcc-graphite@googlegroups.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=simbuerg@googlemail.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).