public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <rguenther@suse.de>
To: Tom de Vries <Tom_deVries@mentor.com>
Cc: "gcc-patches@gnu.org" <gcc-patches@gnu.org>,
	    Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCH] Improve verification of loop->latch in verify_loop_structure
Date: Wed, 25 Nov 2015 10:44:00 -0000	[thread overview]
Message-ID: <alpine.LSU.2.11.1511251144120.4884@t29.fhfr.qr> (raw)
In-Reply-To: <56547D49.5040609@mentor.com>

On Tue, 24 Nov 2015, Tom de Vries wrote:

> [ was: Re: [PATCH] Check NULL loop->latch in verify_loop_structure ]
> 
> On 23/11/15 11:28, Richard Biener wrote:
> > On Mon, 23 Nov 2015, Tom de Vries wrote:
> > 
> > > Hi,
> > > 
> > > In verify_loop_structure, we stop checking the latch once we find that
> > > it's
> > > NULL.
> > > 
> > > This patch tries a bit harder:
> > > - if !LOOPS_MAY_HAVE_MULTIPLE_LATCHES, we don't allow a NULL latch
> > > - if LOOPS_MAY_HAVE_MULTIPLE_LATCHES, we check that indeed there's no
> > >    single loop latch.
> > > 
> > > As a consequence of adding this check, I needed to fix
> > > expand_omp_for_generic,
> > > which missed an initialization of a loop latch.
> > > 
> > > Bootstrapped and reg-tested on x86_64.
> > > 
> > > OK for stage3 trunk?
> > 
> > You miss to catch the case where loop->latch is non-NULL but there
> > are multiple latches, so I think the patch can be improved.
> > That case is more important for correctness (passes
> > seeing ->latch non-NULL assume a single latch).
> > 
> 
> Updated according to comment.
> 
> Bootstrapped and reg-tested on x86_64.
> 
> OK for stage3 trunk?

Ok.

Thanks,
Richard.

  reply	other threads:[~2015-11-25 10:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-22 23:29 [PATCH] Check NULL " Tom de Vries
2015-11-23 10:29 ` Richard Biener
2015-11-24 15:19   ` [PATCH] Improve verification of " Tom de Vries
2015-11-25 10:44     ` Richard Biener [this message]
2015-11-26 11:46       ` Alan Lawrence
2015-11-26 11:57         ` Alan Lawrence
2015-11-26 12:16         ` Richard Biener
2015-11-26 14:44           ` Tom de Vries

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=alpine.LSU.2.11.1511251144120.4884@t29.fhfr.qr \
    --to=rguenther@suse.de \
    --cc=Tom_deVries@mentor.com \
    --cc=gcc-patches@gnu.org \
    --cc=jakub@redhat.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).