public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/109082] emmintrin.h:1624:16: error: argument 3 must be a literal between 0 and 15, inclusive
Date: Mon, 27 Mar 2023 02:45:06 +0000	[thread overview]
Message-ID: <bug-109082-4-zE8zzhX0KL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109082-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109082

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Kewen Lin <linkw@gcc.gnu.org>:

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

commit r13-6870-gf33fc0775706e4db80d584c477608e28f4da0a6f
Author: Kewen Lin <linkw@linux.ibm.com>
Date:   Sun Mar 26 21:42:23 2023 -0500

    rs6000: Ensure vec_sld shift count in allowable range [PR109082]

    As PR109082 shows, some uses of vec_sld in emmintrin.h don't
    strictly guarantee the given shift count is in the range
    0-15 (inclusive).  This patch is to make the argument
    range constraint honored for those uses.

            PR target/109082

    gcc/ChangeLog:

            * config/rs6000/emmintrin.h (_mm_bslli_si128): Check __N is not
less
            than zero when calling vec_sld.
            (_mm_bsrli_si128): Return __A if __N is zero, check __N is bigger
than
            zero when calling vec_sld.
            (_mm_slli_si128): Return __A if _imm5 is zero, check _imm5 is
bigger
            than zero when calling vec_sld.

    gcc/testsuite/ChangeLog:

            * gcc.target/powerpc/pr109082.c: New test.

  parent reply	other threads:[~2023-03-27  2:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-09 15:34 [Bug c/109082] New: " malat at debian dot org
2023-03-09 15:35 ` [Bug c/109082] " malat at debian dot org
2023-03-09 15:44 ` jakub at gcc dot gnu.org
2023-03-09 15:48 ` [Bug target/109082] " jakub at gcc dot gnu.org
2023-03-16  8:14 ` linkw at gcc dot gnu.org
2023-03-27  2:45 ` cvs-commit at gcc dot gnu.org [this message]
2023-03-27  8:10 ` linkw at gcc dot gnu.org

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=bug-109082-4-zE8zzhX0KL@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).