public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/107516] [13 Regression] ICE with -fwide-exec-charset=latin1 Date: Thu, 03 Nov 2022 11:23:26 +0000 [thread overview] Message-ID: <bug-107516-4-ElZVooeXLY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107516-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107516 --- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> --- Maybe a similar issue to PR 81050, i.e. Latin1 isn't valid as a wide charset. In which case, we should give an error instead of ICE if possible. Reduced to remove library headers and C++20 features: template<typename, typename> constexpr bool is_same_v = false; template<typename T> constexpr bool is_same_v<T,T> = true; template<typename CharT> auto units_suffix() noexcept { if constexpr (is_same_v<CharT, wchar_t>) return L"ms"; else return "ms"; } int main() { units_suffix<wchar_t>(); } during RTL pass: expand ice.cc: In function ‘auto units_suffix() [with CharT = wchar_t]’: ice.cc:9:12: internal compiler error: in get_constant_size, at varasm.cc:3418 9 | return L"ms"; | ^~~~~ 0x8a6410 get_constant_size /home/jwakely/src/gcc/gcc/gcc/varasm.cc:3418 0x1519a88 assemble_constant_contents /home/jwakely/src/gcc/gcc/gcc/varasm.cc:3615 0x151af15 output_constant_def_contents /home/jwakely/src/gcc/gcc/gcc/varasm.cc:3666 0x151b264 maybe_output_constant_def_contents /home/jwakely/src/gcc/gcc/gcc/varasm.cc:3602 0x151b264 output_constant_def(tree_node*, int) /home/jwakely/src/gcc/gcc/gcc/varasm.cc:3568 0xe23b2e expand_expr_constant /home/jwakely/src/gcc/gcc/gcc/expr.cc:8592 0xe23b2e expand_expr_addr_expr_1 /home/jwakely/src/gcc/gcc/gcc/expr.cc:8619 0xe24169 expand_expr_addr_expr /home/jwakely/src/gcc/gcc/gcc/expr.cc:8812 0xe19464 expand_expr_real_1(tree_node*, rtx_def*, machine_mode, expand_modifier, rtx_def**, bool) /home/jwakely/src/gcc/gcc/gcc/expr.cc:12096 0xe26825 store_expr(tree_node*, rtx_def*, int, bool, bool) /home/jwakely/src/gcc/gcc/gcc/expr.cc:6330 0xe28090 expand_assignment(tree_node*, tree_node*, bool) /home/jwakely/src/gcc/gcc/gcc/expr.cc:6051 0xcf589c expand_gimple_stmt_1 /home/jwakely/src/gcc/gcc/gcc/cfgexpand.cc:3946 0xcf589c expand_gimple_stmt /home/jwakely/src/gcc/gcc/gcc/cfgexpand.cc:4044 0xcfc0ce expand_gimple_basic_block /home/jwakely/src/gcc/gcc/gcc/cfgexpand.cc:6096 0xcfdbe7 execute /home/jwakely/src/gcc/gcc/gcc/cfgexpand.cc:6822 Please submit a full bug report, with preprocessed source (by using -freport-bug). Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions. And this does ICE "gcc version 12.0.1 20220316 (experimental) (GCC)" so it probably is due to checking.
next prev parent reply other threads:[~2022-11-03 11:23 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-03 11:15 [Bug c++/107516] New: " redi at gcc dot gnu.org 2022-11-03 11:23 ` redi at gcc dot gnu.org [this message] 2022-11-05 10:54 ` [Bug c++/107516] " rguenth at gcc dot gnu.org 2022-11-21 12:56 ` [Bug c++/107516] [13 Regression] ICE with -fwide-exec-charset=latin1 since r9-2891-g5ec9f8cff333bbe9 marxin at gcc dot gnu.org 2022-11-21 15:40 ` [Bug c++/107516] [10/11/12/13 " pinskia at gcc dot gnu.org 2023-01-13 12:35 ` rguenth at gcc dot gnu.org 2023-01-13 12:40 ` jakub at gcc dot gnu.org 2023-07-07 10:44 ` [Bug c++/107516] [11/12/13/14 " 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-107516-4-ElZVooeXLY@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).