public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Roman Gareev <gareevroman@gmail.com>
To: Tobias Grosser <tobias@grosser.es>
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: Sun, 27 Jul 2014 07:33:00 -0000	[thread overview]
Message-ID: <CABGF_gfo2hxbofFTFHDnS=SjUF=fkJaXheeb37fP9qr2c=wLeA@mail.gmail.com> (raw)
In-Reply-To: <53D3BAEB.8000603@grosser.es>

> Can you explain why you believe it is hard/impossible to generate a test
> case without reduction?

I don't believe this. I only know that all the test cases considered
by me have the same problem.

Could you please explain what is 'reduction'? I've found out that,
according to the comment of the rewrite_reductions_out_of_ssa (this
function duplicates pbbs), the rewrite_reductions_out_of_ssa  rewrite
out of SSA all the reduction phi nodes of SCOP. What are reduction phi
nodes? How are they related to 'reduction'?

--
                                   Cheers, Roman Gareev.

  reply	other threads:[~2014-07-27  6:13 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
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 [this message]
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='CABGF_gfo2hxbofFTFHDnS=SjUF=fkJaXheeb37fP9qr2c=wLeA@mail.gmail.com' \
    --to=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).