public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gaius at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug modula2/109810] String literal exceeding array causes ICE Date: Thu, 11 May 2023 11:52:19 +0000 [thread overview] Message-ID: <bug-109810-4-RJFOk26Dd7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109810-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109810 --- Comment #2 from Gaius Mulley <gaius at gcc dot gnu.org> --- gm2 -g highice.mod highice.mod:6:6: warning: string constant is too large to be assigned to the array 6 | a := '12' | ^~ *** WARNING *** there are active plugins, do not report this as a bug unless you can reproduce it without enabling any plugins. Event | Plugins PLUGIN_FINISH | m2rte during GIMPLE pass: lower In function ‘_M2_highice_init’: cc1gm2: internal compiler error: in constant_byte_string, at expr.cc:12378 0x725205 constant_byte_string ../../gcc-13.1.0-RC-20230419/gcc/expr.cc:12378 0x9dde49 c_strlen(tree_node*, int, c_strlen_data*, unsigned int) ../../gcc-13.1.0-RC-20230419/gcc/builtins.cc:609 0xbc4f43 gimple_fold_builtin_memory_op ../../gcc-13.1.0-RC-20230419/gcc/gimple-fold.cc:976 0xbc6b8c gimple_fold_builtin ../../gcc-13.1.0-RC-20230419/gcc/gimple-fold.cc:5018 0xbc6b8c gimple_fold_call ../../gcc-13.1.0-RC-20230419/gcc/gimple-fold.cc:5576 0xbc8a3b fold_stmt_1 ../../gcc-13.1.0-RC-20230419/gcc/gimple-fold.cc:6328 0x1c11ae7 lower_stmt ../../gcc-13.1.0-RC-20230419/gcc/gimple-low.cc:793 0x1c12752 lower_sequence ../../gcc-13.1.0-RC-20230419/gcc/gimple-low.cc:229 0x1c12752 lower_gimple_bind ../../gcc-13.1.0-RC-20230419/gcc/gimple-low.cc:882 0x1c128fb lower_function_body ../../gcc-13.1.0-RC-20230419/gcc/gimple-low.cc:119 0x1c128fb execute ../../gcc-13.1.0-RC-20230419/gcc/gimple-low.cc:206 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
next prev parent reply other threads:[~2023-05-11 11:52 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-11 11:48 [Bug modula2/109810] New: " gaius at gcc dot gnu.org 2023-05-11 11:49 ` [Bug modula2/109810] " gaius at gcc dot gnu.org 2023-05-11 11:52 ` gaius at gcc dot gnu.org [this message] 2023-05-11 22:06 ` gaius at gcc dot gnu.org 2023-05-11 22:08 ` gaius at gcc dot gnu.org 2023-05-11 23:19 ` cvs-commit at gcc dot gnu.org 2023-05-11 23:21 ` gaius at gcc dot gnu.org 2023-07-28 18:28 ` cvs-commit 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-109810-4-RJFOk26Dd7@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).