public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tobias Grosser <tobias@grosser.es>
To: Aditya K <hiraditya@msn.com>, Sebastian Pop <sebpop@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Discard Scops for which entry==exit
Date: Thu, 02 Jul 2015 15:42:00 -0000	[thread overview]
Message-ID: <55955BD6.1020407@grosser.es> (raw)
In-Reply-To: <BLU179-W45A1512E6820B747F23278B6970@phx.gbl>

On 07/02/2015 05:37 PM, Aditya K wrote:
> A test case (gcc/testsuite/gcc.dg/graphite/pr18792.c) came up when we removed `graphite-scop-detection.c:limit_scops'.
> The test case is a scop where entry==exit,
>
> BB5 (*#) -> BB6 (#);
> BB6 -> BB5;
>
> In this case BB2 is out of the scop. This is basically an empty (infinite) loop.

LGTM.

Tobias

      reply	other threads:[~2015-07-02 15:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-29 20:25 Aditya Kumar
2015-06-30  0:13 ` Sebastian Pop
2015-06-30  6:11   ` Tobias Grosser
2015-06-30  7:56     ` Richard Biener
2015-06-30 15:49     ` Aditya K
2015-07-02  7:53       ` Tobias Grosser
2015-07-02 15:37         ` Aditya K
2015-07-02 15:42           ` 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=55955BD6.1020407@grosser.es \
    --to=tobias@grosser.es \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hiraditya@msn.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).