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 <gcc-patches@gcc.gnu.org>,
	Jakub Jelinek <jakub@redhat.com>,
	    schwab@linux-m68k.org
Subject: Re: [PING][PATCH][PR65443] Add transform_to_exit_first_loop_alt
Date: Mon, 08 Jun 2015 11:08:00 -0000	[thread overview]
Message-ID: <alpine.LSU.2.11.1506081246510.30088@zhemvz.fhfr.qr> (raw)
In-Reply-To: <557571B5.1060903@mentor.com>

On Mon, 8 Jun 2015, Tom de Vries wrote:

> On 04/06/15 10:28, Tom de Vries wrote:
> > > I'm ok with the patch and count on you to fix eventual fallout ;)
> > > 
> > 
> > Great, will do.
> 
> And here is the fallout:
> * PR66442 - [6 regression] FAIL: gcc.dg/autopar/pr46885.c (test for
>   excess errors)
> 
> There are two problems in try_transform_to_exit_first_loop_alt:
> 1. In case the latch is not a singleton bb, the function should return
>    false rather than true.
> 2. The check for singleton bb should ignore debug-insns.
> 
> Attached patch fixes these problems.
> 
> Bootstrapped and reg-tested on x86_64.
> 
> Verified by Andreas to fix the problem on m68k.
> 
> OK for trunk?

Ok.

Thanks,
Richard.

  reply	other threads:[~2015-06-08 10:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-27 14:10 [PATCH, stage1][PR65443] " Tom de Vries
2015-04-03 12:40 ` Tom de Vries
2015-04-15 13:39   ` [PING][PATCH][PR65443] " Tom de Vries
2015-04-20 12:26     ` Richard Biener
2015-05-14 11:47       ` Tom de Vries
2015-05-26 11:05         ` Richard Biener
2015-06-04  8:37           ` Tom de Vries
2015-06-08 10:44             ` Tom de Vries
2015-06-08 11:08               ` Richard Biener [this message]
2015-06-08 15:59               ` Thomas Schwinge
2015-06-08 22:12                 ` Tom de Vries
2015-06-09  7:47                   ` Tom de Vries
2015-06-01  8:12         ` [gomp4,committed,PR65443] Add transform_to_exit_first_loop_al 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.1506081246510.30088@zhemvz.fhfr.qr \
    --to=rguenther@suse.de \
    --cc=Tom_deVries@mentor.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=schwab@linux-m68k.org \
    /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).