public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Bill Schmidt <wschmidt@linux.vnet.ibm.com>
Cc: Eric Botcazou <ebotcazou@adacore.com>,
	gcc-patches@gcc.gnu.org,        bergner@vnet.ibm.com,
	steven@gcc.gnu.org, rguenther@suse.de
Subject: Re: [PATCH] Fix PR56605
Date: Wed, 20 Mar 2013 13:50:00 -0000	[thread overview]
Message-ID: <20130320135000.GO12913@tucnak.redhat.com> (raw)
In-Reply-To: <1363787116.4027.53.camel@gnopaine>

On Wed, Mar 20, 2013 at 08:45:16AM -0500, Bill Schmidt wrote:
> Eric, thanks -- fixed in trunk.  Looks like I've missed the window for
> 4.8.0.  Is this OK for backport once 4.8 opens up again?  (Copying
> Richi/Jakub as well.)

Not for 4.8.0 (this isn't a wrong-code, just missed-optimization, right?),
but guess for 4.8.1 it might be ok if it doesn't cause any issues on the
trunk for a few weeks.

> On Mon, 2013-03-18 at 17:31 +0100, Eric Botcazou wrote:
> > > 2013-03-13  Bill Schmidt  <wschmidt@linux.vnet.ibm.com>
> > > 	    Steven Bosscher <steven@gcc.gnu.org>
> > > 
> > > 	PR rtl-optimization/56605
> > > 	* loop-iv.c (implies_p): Handle equal RTXs and subregs.
> > > 
> > > gcc/testsuite:
> > > 
> > > 2013-03-13  Bill Schmidt  wschmidt@linux.vnet.ibm.com>
> > > 
> > > 	PR rtl-optimization/56605
> > > 	* gcc.target/powerpc/pr56605.c: New.
> > 
> > OK, thanks.

	Jakub

  reply	other threads:[~2013-03-20 13:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-13 17:08 Bill Schmidt
     [not found] ` <1452175.pczBboUvvn@polaris>
2013-03-20 13:45   ` Bill Schmidt
2013-03-20 13:50     ` Jakub Jelinek [this message]
2013-03-20 14:00       ` Bill Schmidt

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=20130320135000.GO12913@tucnak.redhat.com \
    --to=jakub@redhat.com \
    --cc=bergner@vnet.ibm.com \
    --cc=ebotcazou@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rguenther@suse.de \
    --cc=steven@gcc.gnu.org \
    --cc=wschmidt@linux.vnet.ibm.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).