public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Peter Bergner <bergner@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r11-8703] rs6000: Harden mma_init_builtins
Date: Wed,  7 Jul 2021 18:33:30 +0000 (GMT)	[thread overview]
Message-ID: <20210707183330.C171D396E849@sourceware.org> (raw)

https://gcc.gnu.org/g:90678482326ef1408748563f190dd7638e7724ee

commit r11-8703-g90678482326ef1408748563f190dd7638e7724ee
Author: Peter Bergner <bergner@linux.ibm.com>
Date:   Wed Jul 7 11:39:34 2021 -0500

    rs6000: Harden mma_init_builtins
    
    The previous MMA patch added some fragile code to initialize its new
    built-ins.  This patch hardens the initialization.
    
    2021-07-07  Peter Bergner  <bergner@linux.ibm.com>
    
    gcc/
            * config/rs6000/rs6000-call.c (mma_init_builtins): Use VSX_BUILTIN_LXVP
            and VSX_BUILTIN_STXVP.
    
    (cherry picked from commit 6278065af07634278ba30029d92a82b089969baa)

Diff:
---
 gcc/config/rs6000/rs6000-call.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/gcc/config/rs6000/rs6000-call.c b/gcc/config/rs6000/rs6000-call.c
index 273cf8927da..7059f4fab1c 100644
--- a/gcc/config/rs6000/rs6000-call.c
+++ b/gcc/config/rs6000/rs6000-call.c
@@ -14318,7 +14318,8 @@ mma_init_builtins (void)
 	  /* Some MMA built-ins that are expanded into gimple are converted
 	     into internal MMA built-ins that are expanded into rtl.
 	     The internal built-in follows immediately after this built-in.  */
-	  if (d[1].icode != CODE_FOR_nothing)
+	  if (d->code != VSX_BUILTIN_LXVP
+	      && d->code != VSX_BUILTIN_STXVP)
 	    {
 	      op[nopnds++] = void_type_node;
 	      icode = d[1].icode;


                 reply	other threads:[~2021-07-07 18:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210707183330.C171D396E849@sourceware.org \
    --to=bergner@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.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).