public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/98914] [11 Regression] ICE in rs6000_expand_vector_set, at config/rs6000/rs6000.c:7198 Date: Wed, 03 Feb 2021 08:15:17 +0000 [thread overview] Message-ID: <bug-98914-4-3n0GyTYNpn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98914-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98914 --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Yeah. The requirement that the index needs to be signed int is fine for the intrinsics, but not otherwise. And if it is an index into a vector with less than 128 elements, one shouldn't care if the index is signed or unsigned char, short, int or long long.
next prev parent reply other threads:[~2021-02-03 8:15 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-01 11:31 [Bug target/98914] New: " asolokha at gmx dot com 2021-02-02 8:12 ` [Bug target/98914] " rguenth at gcc dot gnu.org 2021-02-03 3:59 ` luoxhu at gcc dot gnu.org 2021-02-03 8:11 ` rguenth at gcc dot gnu.org 2021-02-03 8:15 ` jakub at gcc dot gnu.org [this message] 2021-02-04 0:38 ` luoxhu at gcc dot gnu.org 2021-03-22 2:15 ` cvs-commit at gcc dot gnu.org 2021-03-22 2:16 ` luoxhu 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-98914-4-3n0GyTYNpn@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: linkBe 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).