public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/113316] New: during GIMPLE pass: bitintlower ICE: SIGSEGV in var_to_partition (tree-ssa-live.h:163) at -O with uninitialized _BitInt() function argument Date: Wed, 10 Jan 2024 21:19:25 +0000 [thread overview] Message-ID: <bug-113316-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113316 Bug ID: 113316 Summary: during GIMPLE pass: bitintlower ICE: SIGSEGV in var_to_partition (tree-ssa-live.h:163) at -O with uninitialized _BitInt() function argument Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: zsojka at seznam dot cz CC: jakub at gcc dot gnu.org Target Milestone: --- Host: x86_64-pc-linux-gnu Target: x86_64-pc-linux-gnu Created attachment 57030 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57030&action=edit reduced testcase Compiler output: $ x86_64-pc-linux-gnu-gcc -O testcase.c -wrapper valgrind,-q ==9456== Invalid read of size 8 ==9456== at 0x2661471: var_to_partition (tree-ssa-live.h:163) ==9456== by 0x2661471: (anonymous namespace)::bitint_large_huge::lower_call(tree_node*, gimple*) (gimple-lower-bitint.cc:5120) ==9456== by 0x266BF59: gimple_lower_bitint() (gimple-lower-bitint.cc:6514) ==9456== by 0x13CA4BA: execute_one_pass(opt_pass*) (passes.cc:2646) ==9456== by 0x13CADAF: execute_pass_list_1(opt_pass*) (passes.cc:2755) ==9456== by 0x13CADC1: execute_pass_list_1(opt_pass*) (passes.cc:2756) ==9456== by 0x13CADE8: execute_pass_list(function*, opt_pass*) (passes.cc:2766) ==9456== by 0xFCB105: expand (cgraphunit.cc:1842) ==9456== by 0xFCB105: cgraph_node::expand() (cgraphunit.cc:1795) ==9456== by 0xFCC44A: expand_all_functions (cgraphunit.cc:2025) ==9456== by 0xFCC44A: symbol_table::compile() [clone .part.0] (cgraphunit.cc:2399) ==9456== by 0xFCEFC7: compile (cgraphunit.cc:2312) ==9456== by 0xFCEFC7: symbol_table::finalize_compilation_unit() (cgraphunit.cc:2584) ==9456== by 0x150C3E1: compile_file() (toplev.cc:473) ==9456== by 0xDE691B: do_compile (toplev.cc:2151) ==9456== by 0xDE691B: toplev::main(int, char**) (toplev.cc:2307) ==9456== by 0xDE80FA: main (main.cc:39) ==9456== Address 0x0 is not stack'd, malloc'd or (recently) free'd ==9456== during GIMPLE pass: bitintlower testcase.c: In function 'foo': testcase.c:4:1: internal compiler error: Segmentation fault 4 | foo (void) | ^~~ 0x150beff crash_signal /repo/gcc-trunk/gcc/toplev.cc:316 0x2661471 var_to_partition(_var_map*, tree_node*) /repo/gcc-trunk/gcc/tree-ssa-live.h:163 0x2661471 lower_call /repo/gcc-trunk/gcc/gimple-lower-bitint.cc:5120 0x266bf59 gimple_lower_bitint /repo/gcc-trunk/gcc/gimple-lower-bitint.cc:6514 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 reply other threads:[~2024-01-10 21:19 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-10 21:19 zsojka at seznam dot cz [this message] 2024-01-11 13:05 ` [Bug tree-optimization/113316] " jakub at gcc dot gnu.org 2024-01-12 10:19 ` cvs-commit at gcc dot gnu.org 2024-01-12 10:27 ` jakub at gcc dot gnu.org 2024-01-20 17:08 ` pinskia 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-113316-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).