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_if
Date: Sat, 26 Jul 2014 09:26:00 -0000	[thread overview]
Message-ID: <53D37082.30601@grosser.es> (raw)
In-Reply-To: <CABGF_gcBMpPKAHqbN53mVcKvAv32oETnu69nX8rvZjjCViVf3Q@mail.gmail.com>

On 26/07/2014 10:59, Roman Gareev wrote:
> If I'm not mistaken, the reason of this bug is incorrect creation of a
> poly_bb_p for basic_block from the existing pbb in new_pbb_from_pbb
> (It is located in graphite-sese-to-poly.c). I think, that we should
> set a new id of pbb1->domain (instead of using the id of the pbb),
> which contains pointer to the pbb1.
 >
> I found out this after dumping of an index of pbb in the user
> statement S_3. Its index is 9. It is created in
> rewrite_reduction_out_of_ssa using new_pbb_from_pbb and the pbb with
> index 3. After that the user statement S_3 is removed in
> build_scop_drs, but the id of the  pbb->domain and the
> pbb->transformed point to the old pbb with index 3.

Interesting. I was not even aware that we did statement splitting for 
reductions. Very nice analysis.

> I've attached the patch, which may fix this.
>
> --
>                                     Cheers, Roman Gareev.
>
>
> patch.txt
>
>
> Index: gcc/graphite-sese-to-poly.c
> ===================================================================
> --- gcc/graphite-sese-to-poly.c	(revision 212995)
> +++ gcc/graphite-sese-to-poly.c	(working copy)
> @@ -2044,6 +2044,10 @@
>         break;
>
>     pbb1->domain = isl_set_copy (pbb->domain);
> +  char name[50];
> +  snprintf (name, sizeof (name), "S_%d", pbb_index (pbb1));
> +  pbb1->domain = isl_set_set_tuple_id (pbb1->domain,
> +				       isl_id_alloc (scop->ctx, name, pbb1));

Any reason you don't use isl_id_for_pbb() to create this isl_id?

Otherwise, the patch looks good to me. You can commit it if the graphite 
tests still pass and you add an appropriate ChangeLog entry.

Cheers,
Tobias

  reply	other threads:[~2014-07-26  9:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-24 10:10 Roman Gareev
2014-07-24 10:46 ` Tobias Grosser
2014-07-25 11:30   ` Roman Gareev
2014-07-25 11:44     ` Tobias Grosser
2014-07-26  9:07       ` Roman Gareev
2014-07-26  9:26         ` Tobias Grosser [this message]
2014-07-26  9:35 ` Tobias Grosser
2014-07-26 10:24   ` Roman Gareev
2014-07-26 12:59     ` Tobias Grosser
2014-07-26 13:03       ` Roman Gareev
2014-07-26 13:48         ` Tobias Grosser
2014-07-26 13:59           ` Roman Gareev
2014-07-26 14:16             ` Tobias Grosser
2014-07-26 14:28               ` Roman Gareev
2014-07-26 15:05                 ` Tobias Grosser
2014-07-27  7:33                   ` Roman Gareev
2014-07-27  7:34                     ` Tobias Grosser
2014-07-27 10:53                       ` Roman Gareev
2014-07-27 11:02                         ` Tobias Grosser

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=53D37082.30601@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).