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 middle-end/96426] __builtin_convertvector ICE without lhs
Date: Tue, 04 Aug 2020 09:46:14 +0000 [thread overview]
Message-ID: <bug-96426-4-4n5GWHpWw2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96426-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96426
--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:046501dc30f9b0fe31385698af4fd27b464af6ba
commit r10-8570-g046501dc30f9b0fe31385698af4fd27b464af6ba
Author: Jakub Jelinek <jakub@redhat.com>
Date: Tue Aug 4 11:33:18 2020 +0200
veclower: Don't ICE on .VEC_CONVERT calls with no lhs [PR96426]
.VEC_CONVERT is a const internal call, so normally if the lhs is not used,
we'd DCE it far before getting to veclower, but with -O0 (or perhaps
-fno-tree-dce and some other -fno-* options) it can happen.
But as the internal fn needs the lhs to know the type to which the
conversion is done (and I think that is a reasonable representation, having
some magic another argument and having to create constants with that type
looks overkill to me), we just should DCE those calls ourselves.
During veclower, we can't really remove insns, as the callers would be
upset, so this just replaces it with a GIMPLE_NOP.
2020-08-04 Jakub Jelinek <jakub@redhat.com>
PR middle-end/96426
* tree-vect-generic.c (expand_vector_conversion): Replace
.VEC_CONVERT
call with GIMPLE_NOP if there is no lhs.
* gcc.c-torture/compile/pr96426.c: New test.
(cherry picked from commit 95f5a3258dd8a9584f2b10304f79441ef2d4c64c)
next prev parent reply other threads:[~2020-08-04 9:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 8:28 [Bug middle-end/96426] New: " glisse at gcc dot gnu.org
2020-08-03 8:58 ` [Bug middle-end/96426] " rguenth at gcc dot gnu.org
2020-08-04 9:33 ` cvs-commit at gcc dot gnu.org
2020-08-04 9:46 ` cvs-commit at gcc dot gnu.org [this message]
2020-09-16 19:22 ` cvs-commit at gcc dot gnu.org
2021-08-07 19:59 ` pinskia at gcc dot gnu.org
2021-08-07 19:59 ` pinskia 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-96426-4-4n5GWHpWw2@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).