public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pthaugen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/109491] New: Segfault in tree-ssa-sccvn.cc:expressions_equal_p() Date: Wed, 12 Apr 2023 20:25:42 +0000 [thread overview] Message-ID: <bug-109491-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109491 Bug ID: 109491 Summary: Segfault in tree-ssa-sccvn.cc:expressions_equal_p() Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: pthaugen at gcc dot gnu.org CC: bergner at gcc dot gnu.org, segher at kernel dot crashing.org Target Milestone: --- Host: powerpc64 Target: powerpc64 Build: powerpc64 Created attachment 54845 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54845&action=edit Reduced testcase Hitting the following segfault on the attached testcase (sorry for size, but it is about 1% of original size). Appears to only happen with GCC 13, compiles fine with GCC 12. ~/install/gcc/trunk/bin/g++ -mcpu=power8 -std=c++14 -S -O2 partial.ii (...misc warnings...) during GIMPLE pass: fre partial.ii: In function ‘void gemm_complex(const DataMapper&, const complex<float>*, const complex<float>*, long int, long int, long int, complex<float>, long int, long int, long int, long int) [with <template-parameter-1-1> = complex<float>; <template-parameter-1-2> = complex<float>; <template-parameter-1-3> = complex<float>; <template-parameter-1-4> = float; Packet = __vector(4) float; Packetc = Packet2cf; <template-parameter-1-7> = __vector(4) float; DataMapper = blas_data_mapper; int accRows = 4; int accCols = 4; int ConjugateLhs = 0; int ConjugateRhs = 0; int LhsIsReal = 0; int RhsIsReal = 0]’: partial.ii:1096:6: internal compiler error: Segmentation fault 1096 | void gemm_complex(const DataMapper &res, const complex<float> *blockAc, | ^~~~~~~~~~~~ 0x10f6fadb crash_signal /home/pthaugen/src/gcc/trunk/gcc/gcc/toplev.cc:314 0x11222818 expressions_equal_p(tree_node*, tree_node*, bool) /home/pthaugen/src/gcc/trunk/gcc/gcc/tree-ssa-sccvn.cc:6411 0x112229a7 vn_reference_op_eq /home/pthaugen/src/gcc/trunk/gcc/gcc/tree-ssa-sccvn.cc:216 0x11222bfb vn_reference_eq(vn_reference_s const*, vn_reference_s const*) /home/pthaugen/src/gcc/trunk/gcc/gcc/tree-ssa-sccvn.cc:858 0x11243837 vn_reference_hasher::equal(vn_reference_s const*, vn_reference_s const*) /home/pthaugen/src/gcc/trunk/gcc/gcc/tree-ssa-sccvn.cc:250 0x11243837 hash_table<vn_reference_hasher, false, xcallocator>::find_slot_with_hash(vn_reference_s* const&, unsigned int, insert_option) /home/pthaugen/src/gcc/trunk/gcc/gcc/hash-table.h:1059 0x1122f43b vn_reference_lookup_2 /home/pthaugen/src/gcc/trunk/gcc/gcc/tree-ssa-sccvn.cc:2336 0x11101b8f walk_non_aliased_vuses(ao_ref*, tree_node*, bool, void* (*)(ao_ref*, tree_node*, void*), void* (*)(ao_ref*, tree_node*, void*, translate_flags*), tree_node* (*)(tree_node*), unsigned int&, void*) /home/pthaugen/src/gcc/trunk/gcc/gcc/tree-ssa-alias.cc:3847 0x11233447 vn_reference_lookup(tree_node*, tree_node*, vn_lookup_kind, vn_reference_s**, bool, tree_node**, tree_node*, bool) /home/pthaugen/src/gcc/trunk/gcc/gcc/tree-ssa-sccvn.cc:3967 0x11238cc7 visit_reference_op_load /home/pthaugen/src/gcc/trunk/gcc/gcc/tree-ssa-sccvn.cc:5683 0x11238cc7 visit_stmt /home/pthaugen/src/gcc/trunk/gcc/gcc/tree-ssa-sccvn.cc:6187 0x1123986f process_bb /home/pthaugen/src/gcc/trunk/gcc/gcc/tree-ssa-sccvn.cc:7918 0x1123bcdb do_rpo_vn_1 /home/pthaugen/src/gcc/trunk/gcc/gcc/tree-ssa-sccvn.cc:8518 0x1123db83 execute /home/pthaugen/src/gcc/trunk/gcc/gcc/tree-ssa-sccvn.cc:8676 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:[~2023-04-12 20:25 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-12 20:25 pthaugen at gcc dot gnu.org [this message] 2023-04-12 20:26 ` [Bug tree-optimization/109491] [13 Regression] " pinskia at gcc dot gnu.org 2023-04-12 20:46 ` pthaugen at gcc dot gnu.org 2023-04-12 20:52 ` pinskia at gcc dot gnu.org 2023-04-12 20:54 ` pinskia at gcc dot gnu.org 2023-04-12 21:08 ` bergner at gcc dot gnu.org 2023-04-12 21:16 ` pthaugen at gcc dot gnu.org 2023-04-13 11:34 ` rguenth at gcc dot gnu.org 2023-04-13 11:35 ` rguenth at gcc dot gnu.org 2023-04-13 12:07 ` rguenth at gcc dot gnu.org 2023-04-13 12:17 ` rguenth at gcc dot gnu.org 2023-04-13 13:00 ` cvs-commit at gcc dot gnu.org 2023-04-13 13:01 ` [Bug tree-optimization/109491] [11/12 " rguenth at gcc dot gnu.org 2023-04-13 16:22 ` chip.kerchner at ibm dot com 2023-04-14 7:17 ` rguenth at gcc dot gnu.org 2023-04-14 12:24 ` chip.kerchner at ibm dot com 2023-04-14 12:45 ` rguenther at suse dot de 2023-04-14 13:15 ` rguenth at gcc dot gnu.org 2023-04-14 13:32 ` hubicka at gcc dot gnu.org 2023-04-17 9:14 ` cvs-commit at gcc dot gnu.org 2023-04-17 10:44 ` [Bug tree-optimization/109491] [11 " cvs-commit at gcc dot gnu.org 2023-04-17 10:46 ` 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-109491-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).