public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tobias Grosser <tobias@grosser.es>
To: Roman Gareev <gareevroman@gmail.com>
Cc: Mircea Namolaru <mircea.namolaru@inria.fr>, gcc-patches@gcc.gnu.org
Subject: Re: [GSoC] generation of Gimple code from isl_ast_node_block
Date: Tue, 22 Jul 2014 16:56:00 -0000	[thread overview]
Message-ID: <53CE925C.4020203@grosser.es> (raw)
In-Reply-To: <CABGF_gcGzThs5+R4ki8pCsF5hwWasbKEStjPT+7trC00b=MwYA@mail.gmail.com>

On 22/07/2014 18:00, Roman Gareev wrote:
> I've attached the patch, which contains generation of Gimple code from
> isl_ast_node_block. Is it fine for trunk?

LGTM.

Tobias

  reply	other threads:[~2014-07-22 16:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-22 16:04 Roman Gareev
2014-07-22 16:56 ` Tobias Grosser [this message]
2014-07-23  9:16 ` Rainer Orth
2014-07-23  9:37   ` Tobias Grosser
2014-07-23 15:09     ` Roman Gareev

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=53CE925C.4020203@grosser.es \
    --to=tobias@grosser.es \
    --cc=gareevroman@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mircea.namolaru@inria.fr \
    /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).