From: Sebastian Pop <sebpop@gmail.com>
To: Tobias Grosser <tobias@grosser.es>
Cc: Roman Gareev <gareevroman@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Mircea Namolaru <mircea.namolaru@inria.fr>
Subject: Re: [GSoC] Addition of ISL AST generation to Graphite
Date: Mon, 23 Jun 2014 09:30:00 -0000 [thread overview]
Message-ID: <CAFk3UF9KO7Jodwno__0xpHcmG_Wij8Y6k3VZoRXreduryCtMgg@mail.gmail.com> (raw)
In-Reply-To: <53A1E2B9.3090205@grosser.es>
Please add a FIXME note in graphite_regenerate_ast_isl saying that
this is not yet a full implementation of the code generator with ISL
ASTs.
It would be useful to make the current graphite_regenerate_ast_isl
working by calling graphite_regenerate_ast_cloog and adding the fixme
note above saying that we rely on the cloog code generator until we
implement the ISL AST parsing.
There is also a minor code style issue in:
isl_set * context_isl = isl_set_params (isl_set_copy (scop->context));
please remove the space after *:
isl_set *context_isl = isl_set_params (isl_set_copy (scop->context));
Otherwise the two patches look good to me.
Thanks,
Sebastian
On Wed, Jun 18, 2014 at 12:04 PM, Tobias Grosser <tobias@grosser.es> wrote:
> On 18/06/2014 21:00, Roman Gareev wrote:
>>
>> These patches add ISL AST generation to graphite, which can be chosen
>> by the fgraphite-code-generator=[isl|cloog] switch. The first patch
>> makes initial renaming of gloog and gloog_error to
>> graphite_regenerate_ast_cloog and graphite_regenerate_error,
>> respectively. The second one adds new files with generation of ISL
>> AST, new switch, new testcase that checks that the dump is generated.
>>
>> Is it fine for trunk?
>
>
> I went over this from the graphite side and it looks fine. However,
> as I did not commit for a while to gcc, it would be great if someone else
> could have a look.
>
> Cheers,
> Tobias
>
next prev parent reply other threads:[~2014-06-23 9:30 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 [this message]
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
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=CAFk3UF9KO7Jodwno__0xpHcmG_Wij8Y6k3VZoRXreduryCtMgg@mail.gmail.com \
--to=sebpop@gmail.com \
--cc=gareevroman@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mircea.namolaru@inria.fr \
--cc=tobias@grosser.es \
/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).