public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tobias Grosser <tobias@grosser.es>
To: Sebastian Pop <s.pop@samsung.com>, gcc-patches@gcc.gnu.org
Cc: sebpop@gmail.com, aditya.k7@samsung.com, richard.guenther@gmail.com
Subject: Re: [PATCH 2/2] call scev analysis in scop-detection as in sese-to-poly
Date: Thu, 01 Oct 2015 08:00:00 -0000	[thread overview]
Message-ID: <560CE82C.7010703@grosser.es> (raw)
In-Reply-To: <1443651097-407-2-git-send-email-s.pop@samsung.com>

On 10/01/2015 12:11 AM, Sebastian Pop wrote:
> Before our rewrite of the scop detection, we used to not have a valid SESE
> region under hand, and so we used to do more ad-hoc analysis of data references
> by trying to prove that at all levels of a loop nest the data references would
> be still valid.
>
> Now that we have a valid SESE region, we can call the scev analysis in the same
> way on the same computed loop nest in the scop-detection as in the sese-to-poly.
>
> Next step will be to cache the data references analyzed in the scop detection
> and not compute the same info in sese-to-poly.
>
> The patch fixes block-1.f90 that used to ICE on x86_64-linux when compiled with
> -m32.  Patch passed bootstrap with BOOT_CFLAGS="-g -O2 -fgraphite-identity
> -floop-nest-optimize" and check on x86_64-linux using ISL-0.15.

Nice.

Tobias

      parent reply	other threads:[~2015-10-01  8:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-30 23:58 [PATCH 1/2] add recursion on the inner loops Sebastian Pop
     [not found] ` <1443651097-407-2-git-send-email-s.pop@samsung.com>
2015-10-01  8:00   ` Tobias Grosser [this message]

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=560CE82C.7010703@grosser.es \
    --to=tobias@grosser.es \
    --cc=aditya.k7@samsung.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=richard.guenther@gmail.com \
    --cc=s.pop@samsung.com \
    --cc=sebpop@gmail.com \
    /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).