public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bill Schmidt <wschmidt@linux.vnet.ibm.com>
To: jakub@redhat.com, rguenther@suse.de
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	       Ulrich Weigand	 <Ulrich.Weigand@de.ibm.com>,
	       David Edelsohn <dje.gcc@gmail.com>
Subject: Re: [PATCH, rs6000] Fix PR65914
Date: Mon, 22 Jun 2015 03:00:00 -0000	[thread overview]
Message-ID: <1434937630.2747.77.camel@gnopaine> (raw)
In-Reply-To: <CAGWvny=wkhk=sQHW5phrKw=6M9ZgwBcoix8qBYJ_5-QUWvFJRg@mail.gmail.com>

On Fri, 2015-06-19 at 20:36 -0400, David Edelsohn wrote:
> On Fri, Jun 19, 2015 at 6:35 PM, Bill Schmidt
> <wschmidt@linux.vnet.ibm.com> wrote:
> > Hi,
> >
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65914 demonstrates that we
> > fail to match vector predicates with pseudos that are in the virtual
> > stack register range.  The reduced test case provided with the bug
> > report, when compiled for the C++14 standard, demonstrates that we need
> > to be able to do this.  This patch loosens the restriction for the
> > vector predicates so that all pseudos are accepted.  Thanks to Uli
> > Weigand for his insights on this bug.
> >
> > As a side benefit, applying this patch fixes a number of libgomp tests
> > that have been failing recently.
> >
> > Bootstrapped and tested on powerpc64le-unknown-linux-gnu with no
> > regressions.  Is this ok for trunk?  After it burns in, I would propose
> > to backport it to GCC 5.1 and GCC 4.9 (when the tree is open).
> >
> > Thanks,
> > Bill
> >
> >
> > [gcc]
> >
> > 2015-05-19  Bill Schmidt  <wschmidt@linux.vnet.ibm.com>
> >
> >         * config/rs6000/predicates.md (altivec_register_operand): Permit
> >         virtual stack registers.
> >         (vsx_register_operand): Likewise.
> >         (vfloat_operand): Likewise.
> >         (vint_operand): Likewise.
> >         (vlogical_operand): Likewise.
> 
> Okay.
> 
> > [gcc/testsuite]
> >
> > 2015-05-19  Bill Schmidt  <wschmidt@linux.vnet.ibm.com>
> >
> >         * g++.dg/torture/pr65419.C:  New.
> 
> Maybe you should ask Richi or Jakub about the testcase because you are
> placing it in a non-target-specific location.  It should succeed on
> all targets, but it may expose latent bugs on other targets.

OK, thanks.  Richi, Jakub, is this ok as a general C++ torture test?

Thanks,
Bill

> 
> Thanks, David
> 


  parent reply	other threads:[~2015-06-22  1:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-19 23:32 Bill Schmidt
2015-06-20  6:09 ` David Edelsohn
2015-06-21  9:48   ` Mike Stump
2015-06-21 13:57     ` Bill Schmidt
2015-06-22  3:00   ` Bill Schmidt [this message]
2015-06-22  6:57     ` Jakub Jelinek

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=1434937630.2747.77.camel@gnopaine \
    --to=wschmidt@linux.vnet.ibm.com \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=rguenther@suse.de \
    /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).