public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/113013] New: [12/13/14 regression] ICE in fold_convert_loc with -fsanitize=undefined Date: Thu, 14 Dec 2023 03:10:31 +0000 [thread overview] Message-ID: <bug-113013-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113013 Bug ID: 113013 Summary: [12/13/14 regression] ICE in fold_convert_loc with -fsanitize=undefined Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: sjames at gcc dot gnu.org Target Milestone: --- Created attachment 56876 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56876&action=edit reduced.i Hit this when reducing PR113012. ``` $ gcc -c /tmp/foo.c -O2 -fsanitize=undefined during GIMPLE pass: objsz /tmp/foo.c: In function ‘miZeroLine_list_len’: /tmp/foo.c:9:6: internal compiler error: in fold_convert_loc, at fold-const.cc:2602 9 | void miZeroLine_list_len() { | ^~~~~~~~~~~~~~~~~~~ 0x55eb4274eca3 fold_convert_loc(unsigned int, tree_node*, tree_node*) /usr/src/debug/sys-devel/gcc-14.0.0_pre20231210/gcc-14-20231210/gcc/fold-const.cc:2602 0x55eb446f7d13 alloc_object_size /usr/src/debug/sys-devel/gcc-14.0.0_pre20231210/gcc-14-20231210/gcc/tree-object-size.cc:811 0x55eb446f7d13 call_object_size /usr/src/debug/sys-devel/gcc-14.0.0_pre20231210/gcc-14-20231210/gcc/tree-object-size.cc:1339 0x55eb446f7d13 collect_object_sizes_for /usr/src/debug/sys-devel/gcc-14.0.0_pre20231210/gcc-14-20231210/gcc/tree-object-size.cc:1779 0x55eb4418920f compute_builtin_object_size(tree_node*, int, tree_node**) /usr/src/debug/sys-devel/gcc-14.0.0_pre20231210/gcc-14-20231210/gcc/tree-object-size.cc:1194 0x55eb43fab777 fold_builtin_object_size /usr/src/debug/sys-devel/gcc-14.0.0_pre20231210/gcc-14-20231210/gcc/builtins.cc:11556 0x55eb43fab777 fold_builtin_2 /usr/src/debug/sys-devel/gcc-14.0.0_pre20231210/gcc-14-20231210/gcc/builtins.cc:10575 0x55eb43fab777 fold_builtin_n(unsigned int, tree_node*, tree_node*, tree_node**, int, bool) [clone .isra.0] /usr/src/debug/sys-devel/gcc-14.0.0_pre20231210/gcc-14-20231210/gcc/builtins.cc:10687 0x55eb440cd22d dynamic_object_sizes_execute_one /usr/src/debug/sys-devel/gcc-14.0.0_pre20231210/gcc-14-20231210/gcc/tree-object-size.cc:2078 0x55eb440cd22d object_sizes_execute /usr/src/debug/sys-devel/gcc-14.0.0_pre20231210/gcc-14-20231210/gcc/tree-object-size.cc:2140 Please submit a full bug report, with preprocessed source (by using -freport-bug). Please include the complete backtrace with any bug report. See <https://bugs.gentoo.org/> for instructions. ```
next reply other threads:[~2023-12-14 3:10 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-14 3:10 sjames at gcc dot gnu.org [this message] 2023-12-14 3:17 ` [Bug tree-optimization/113013] " pinskia at gcc dot gnu.org 2023-12-14 3:18 ` pinskia at gcc dot gnu.org 2023-12-14 3:20 ` pinskia at gcc dot gnu.org 2023-12-14 12:52 ` siddhesh at gcc dot gnu.org 2023-12-14 14:00 ` rguenth at gcc dot gnu.org 2023-12-15 13:28 ` jakub at gcc dot gnu.org 2023-12-15 13:54 ` siddhesh at gcc dot gnu.org 2023-12-18 9:00 ` cvs-commit at gcc dot gnu.org 2023-12-18 9:14 ` cvs-commit at gcc dot gnu.org 2023-12-18 9:26 ` cvs-commit at gcc dot gnu.org 2023-12-18 9:38 ` jakub 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-113013-4@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).