public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: William Schmidt <wschmidt@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-6043] rs6000: Fix fake vec_promote overload
Date: Fri, 17 Dec 2021 16:39:13 +0000 (GMT)	[thread overview]
Message-ID: <20211217163913.5A7193858410@sourceware.org> (raw)

https://gcc.gnu.org/g:dfedfc304ad2159acbff1d89e707e359e97353bf

commit r12-6043-gdfedfc304ad2159acbff1d89e707e359e97353bf
Author: Bill Schmidt <wschmidt@linux.ibm.com>
Date:   Fri Dec 17 10:39:00 2021 -0600

    rs6000: Fix fake vec_promote overload
    
    rs6000-overload.def defines one instance of vec_promote so that it can be
    registered with the front end.  Actual expansion of the vec_promote overload
    is done with special-case code in rs6000-c.c.  During another cleanup, I
    observed that the fake instance has the wrong number of arguments.  Fix that.
    
    2021-12-17  Bill Schmidt  <wschmidt@linux.ibm.com>
    
    gcc/
            * config/rs6000/rs6000-overload.def (__builtin_vec_promote): Add second
            argument.

Diff:
---
 gcc/config/rs6000/rs6000-overload.def | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/config/rs6000/rs6000-overload.def b/gcc/config/rs6000/rs6000-overload.def
index 531a4fcd1af..2b2853918c0 100644
--- a/gcc/config/rs6000/rs6000-overload.def
+++ b/gcc/config/rs6000/rs6000-overload.def
@@ -3021,7 +3021,7 @@
 ; is replaced by a constructor.  The single overload here causes
 ; __builtin_vec_promote to be registered with the front end so that can happen.
 [VEC_PROMOTE, vec_promote, __builtin_vec_promote]
-  vsi __builtin_vec_promote (vsi);
+  vsi __builtin_vec_promote (vsi, const int);
     ABS_V4SI PROMOTE_FAKERY
 
 [VEC_RE, vec_re, __builtin_vec_re]


                 reply	other threads:[~2021-12-17 16:39 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=20211217163913.5A7193858410@sourceware.org \
    --to=wschmidt@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).