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 c++/106001] [12/13 Regression] ICE: expected expression 'static_cast<char>(1)' of kind static_cast_expr since r12-1128-gef8176e0fac935
Date: Fri, 17 Jun 2022 15:41:24 +0000 [thread overview]
Message-ID: <bug-106001-4-LRwI9rycEv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106001-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106001
--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:a284fadcce8ef443cc3cc047a8017745efb51758
commit r13-1158-ga284fadcce8ef443cc3cc047a8017745efb51758
Author: Jakub Jelinek <jakub@redhat.com>
Date: Fri Jun 17 17:40:49 2022 +0200
c++: Use fold_non_dependent_expr rather than maybe_constant_value in
__builtin_shufflevector handling [PR106001]
In this case the STATIC_CAST_EXPR expressions in the call aren't
type nor value dependent, but maybe_constant_value still ICEs on those
when processing_template_decl. Calling fold_non_dependent_expr on it
instead fixes the ICE and folds them to INTEGER_CSTs.
2022-06-17 Jakub Jelinek <jakub@redhat.com>
PR c++/106001
* typeck.cc (build_x_shufflevector): Use fold_non_dependent_expr
instead of maybe_constant_value.
* g++.dg/ext/builtin-shufflevector-4.C: New test.
next prev parent reply other threads:[~2022-06-17 15:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 13:05 [Bug c++/106001] New: [12 Regression] ICE: nexpected expression 'static_cast<char>(1)' of kind static_cast_expr doko at gcc dot gnu.org
2022-06-16 13:41 ` [Bug c++/106001] [12/13 " mpolacek at gcc dot gnu.org
2022-06-16 17:30 ` [Bug c++/106001] [12/13 Regression] ICE: expected expression 'static_cast<char>(1)' of kind static_cast_expr since r12-1128-gef8176e0fac935 jakub at gcc dot gnu.org
2022-06-16 17:51 ` jakub at gcc dot gnu.org
2022-06-17 15:41 ` cvs-commit at gcc dot gnu.org [this message]
2022-06-19 10:09 ` cvs-commit at gcc dot gnu.org
2022-06-20 9:50 ` rguenth 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-106001-4-LRwI9rycEv@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).