From: Tobias Grosser <tobias@grosser.es>
To: Roman Gareev <gareevroman@gmail.com>
Cc: Mircea Namolaru <mircea.namolaru@inria.fr>,
Richard Biener <richard.guenther@gmail.com>,
kyrylo.tkachov@arm.com, Rainer Orth <ro@cebitec.uni-bielefeld.de>,
gcc-patches@gcc.gnu.org
Subject: Re: [GSoC] Addition of ISL AST generation to Graphite
Date: Thu, 17 Jul 2014 14:26:00 -0000 [thread overview]
Message-ID: <53C7DAF5.7080305@grosser.es> (raw)
In-Reply-To: <CABGF_gc+eBhJyVOea4i4Yj2UA0LSr7z72rOh-ZE7YhmCQaXryw@mail.gmail.com>
On 17/07/2014 16:11, Roman Gareev wrote:
> I've attached the patch, which adds the requirement for isl 0.12.
> Tobias, is it important to accept only 0.12.1, 0.12.2 and forbid 0.12?
I am not aware of any problems with isl 0.12 and would be surprised if
such problems exist. Are you?
The patch itself looks good. As it is trivial, fixing an annoying
bootstrapping bug, and people agreed that this is the right direction, I
propose that you commit it right ahead.
Further reviews are still welcome.
Cheers,
Tobias
P.S: As Richard suggested, we may also want to forbid CLooG 0.17.
next prev parent reply other threads:[~2014-07-17 14:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 19:00 Roman Gareev
2014-06-18 19:04 ` Tobias Grosser
2014-06-23 9:30 ` Sebastian Pop
2014-06-23 9:35 ` Tobias Grosser
2014-06-23 12:46 ` Roman Gareev
[not found] ` <53A82B9A.5000104@grosser.es>
2014-06-23 13:37 ` Roman Gareev
2014-07-04 12:58 ` Rainer Orth
2014-07-05 20:21 ` Rainer Orth
2014-07-06 6:55 ` Roman Gareev
2014-07-14 10:45 ` Kyrill Tkachov
2014-07-15 15:03 ` Roman Gareev
2014-07-15 15:48 ` Tobias Grosser
2014-07-16 9:42 ` Richard Biener
2014-07-16 9:46 ` Tobias Grosser
2014-07-16 12:10 ` Roman Gareev
2014-07-16 13:23 ` Tobias Grosser
2014-07-17 14:17 ` Roman Gareev
2014-07-17 14:26 ` Tobias Grosser [this message]
2014-07-20 11:39 ` Roman Gareev
2014-07-20 15:09 ` Tobias Grosser
2014-06-29 17:31 Gerald Pfeifer
2014-06-29 17:39 ` Tobias Grosser
2014-06-29 20:44 ` Gerald Pfeifer
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=53C7DAF5.7080305@grosser.es \
--to=tobias@grosser.es \
--cc=gareevroman@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kyrylo.tkachov@arm.com \
--cc=mircea.namolaru@inria.fr \
--cc=richard.guenther@gmail.com \
--cc=ro@cebitec.uni-bielefeld.de \
/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).