From: David Edelsohn <dje.gcc@gmail.com>
To: Peter Bergner <bergner@linux.ibm.com>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Bill Schmidt <wschmidt@linux.ibm.com>,
Rajalakshmi Srinivasaraghavan <raji@linux.ibm.com>
Subject: Re: [PATCH] rs6000: Fix ICE expanding lxvp and stxvp gimple built-ins [PR101849]
Date: Thu, 12 Aug 2021 14:20:00 -0400 [thread overview]
Message-ID: <CAGWvnynYj+LTv93XvDfWC8ZMq+OsEZOSV88mw4BQ4ZHSKnQxyQ@mail.gmail.com> (raw)
In-Reply-To: <642de18f-8175-27ca-9a97-d68cd172aa98@linux.ibm.com>
On Tue, Aug 10, 2021 at 7:37 PM Peter Bergner <bergner@linux.ibm.com> wrote:
>
> PR101849 shows we ICE on a test case when we pass a non __vector_pair *
> pointer to the __builtin_vsx_lxvp and __builtin_vsx_stxvp built-ins
> that is cast to __vector_pair *. The problem is that when we expand
> the built-in, the cast has already been removed from gimple and we are
> only given the base pointer. The solution used here (which fixes the ICE)
> is to catch this case and convert the pointer to a __vector_pair * pointer
> when expanding the built-in.
>
> This passed bootstrap and regression testing on powerpc64le-linux with
> no regressions. Ok for mainline? This also affects GCC 11 and 10, so
> ok there too after it has baked on trunk for a few days?
>
> Peter
>
>
> gcc/
> PR target/101849
> * config/rs6000/rs6000-call.c (rs6000_gimple_fold_mma_builtin): Cast
> pointer to __vector_pair *.
>
> gcc/testsuite/
> PR target/101849
> * gcc.target/powerpc/pr101849.c: New test.
Okay.
Thanks, David
next prev parent reply other threads:[~2021-08-12 18:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 23:37 Peter Bergner
2021-08-11 16:40 ` Bill Schmidt
2021-08-12 18:20 ` David Edelsohn [this message]
2021-08-13 17:01 ` Peter Bergner
2021-08-13 17:15 ` Bill Schmidt
2021-08-19 23:36 ` Peter Bergner
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=CAGWvnynYj+LTv93XvDfWC8ZMq+OsEZOSV88mw4BQ4ZHSKnQxyQ@mail.gmail.com \
--to=dje.gcc@gmail.com \
--cc=bergner@linux.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=raji@linux.ibm.com \
--cc=segher@kernel.crashing.org \
--cc=wschmidt@linux.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).