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/91903] vec_ctf altivec intrinsic can cause ICE on powerpc
Date: Fri, 29 Jan 2021 17:40:51 +0000	[thread overview]
Message-ID: <bug-91903-4-he67CQUXZY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-91903-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Will Schmidt <willschm@gcc.gnu.org>:

https://gcc.gnu.org/g:91a95ad2ae0e0f2fa953fafe55ff2ec32c8277d5

commit r11-6984-g91a95ad2ae0e0f2fa953fafe55ff2ec32c8277d5
Author: Will Schmidt <will_schmidt@vnet.ibm.com>
Date:   Fri Oct 23 17:28:17 2020 -0500

    [PATCH, rs6000] improve vec_ctf invalid parameter handling.

    Hi,
      Per PR91903, GCC ICEs when we attempt to pass a variable
    (or out of range value) into the vec_ctf() builtin.  Per
    investigation, the parameter checking exists for this
    builtin with the int types, but was missing for
    the long long types. This problem also occurs for the
    vec_cts() builtin, which is also fixed by this patch.

    This patch adds the missing CODE_FOR_* entries to the
    rs6000_expand_binup_builtin to cover that scenario.
    This patch also updates some existing tests to remove
    calls to vec_ctf() and vec_cts() that contain negative
    values.

    PR target/91903

    2020-01-29  Will Schmidt  <will_schmidt@vnet.ibm.com>

    gcc/ChangeLog:
            * config/rs6000/rs6000-call.c (rs6000_expand_binup_builtin): Add
            clauses for CODE_FOR_vsx_xvcvuxddp_scale and
            CODE_FOR_vsx_xvcvsxddp_scale to the parameter checking code.

    gcc/testsuite/ChangeLog:
            * gcc.target/powerpc/pr91903.c: New test.
            * gcc.target/powerpc/builtins-1.fold.h: Update.
            * gcc.target/powerpc/builtins-2.c: Update.

       reply	other threads:[~2021-01-29 17:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-91903-4@http.gcc.gnu.org/bugzilla/>
2021-01-29 17:40 ` cvs-commit at gcc dot gnu.org [this message]
2021-04-27 11:38 ` jakub at gcc dot gnu.org
2021-05-04 12:31 ` rguenth at gcc dot gnu.org
2021-07-28  7:04 ` rguenth at gcc dot gnu.org
2022-02-17 17:39 ` segher 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-91903-4-he67CQUXZY@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).