public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/99106] New: ICE in tree_to_poly_int64, at tree.c:3091 Date: Mon, 15 Feb 2021 14:23:03 +0000 [thread overview] Message-ID: <bug-99106-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99106 Bug ID: 99106 Summary: ICE in tree_to_poly_int64, at tree.c:3091 Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: marxin at gcc dot gnu.org CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot gnu.org Target Milestone: --- Started with the same revision as PR99033: $ g++ /home/marxin/Programming/gcc/gcc/testsuite/g++.dg/ext/flexary38.C -c -fsanitize=undefined during GIMPLE pass: ubsan /home/marxin/Programming/gcc/gcc/testsuite/g++.dg/ext/flexary38.C: In function ‘void foo()’: /home/marxin/Programming/gcc/gcc/testsuite/g++.dg/ext/flexary38.C:18:1: internal compiler error: in tree_to_poly_int64, at tree.c:3091 18 | } | ^ 0x87f81e tree_to_poly_int64(tree_node const*) /home/marxin/Programming/gcc/gcc/tree.c:3091 0x87f81e tree_to_poly_int64(tree_node const*) /home/marxin/Programming/gcc/gcc/tree.c:3089 0x148775e component_ref_size(tree_node*, special_array_member*) /home/marxin/Programming/gcc/gcc/tree.c:13920 0x1232ece decl_init_size(tree_node*, bool) /home/marxin/Programming/gcc/gcc/tree-object-size.c:196 0x12336ca addr_object_size /home/marxin/Programming/gcc/gcc/tree-object-size.c:285 0x123556b compute_builtin_object_size(tree_node*, int, unsigned long*, tree_node**, tree_node**) /home/marxin/Programming/gcc/gcc/tree-object-size.c:570 0x11a6565 instrument_object_size /home/marxin/Programming/gcc/gcc/ubsan.c:2150 0x11ab575 execute /home/marxin/Programming/gcc/gcc/ubsan.c:2405 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions.
next reply other threads:[~2021-02-15 14:23 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-15 14:23 marxin at gcc dot gnu.org [this message] 2021-02-16 7:23 ` [Bug sanitizer/99106] [9/10/11 Regression] " rguenth at gcc dot gnu.org 2021-02-16 15:30 ` jakub at gcc dot gnu.org 2021-02-17 14:04 ` cvs-commit at gcc dot gnu.org 2021-02-22 16:50 ` [Bug sanitizer/99106] [9/10 " jakub at gcc dot gnu.org 2021-03-19 23:29 ` cvs-commit at gcc dot gnu.org 2021-03-20 8:08 ` [Bug sanitizer/99106] [9 " jakub at gcc dot gnu.org 2021-04-20 23:32 ` cvs-commit at gcc dot gnu.org 2021-04-22 16:50 ` cvs-commit at gcc dot gnu.org 2021-04-22 17:11 ` 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-99106-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).