public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "wojciech_mula at poczta dot onet.pl" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/114172] [13 only] ICE with riscv rvv VSETVL intrinsic Date: Fri, 29 Mar 2024 02:05:39 +0000 [thread overview] Message-ID: <bug-114172-4-hs3mF3eLk9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114172-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114172 Wojciech Mula <wojciech_mula at poczta dot onet.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wojciech_mula at poczta dot onet.p | |l --- Comment #2 from Wojciech Mula <wojciech_mula at poczta dot onet.pl> --- Checked 13.2 from Debian: $ riscv64-linux-gnu-gcc --version riscv64-linux-gnu-gcc (Debian 13.2.0-12) 13.2.0 For the Bruce's testcase the following invocation triggers segfault (-O2, -O1, -O2 - no error): $ riscv64-linux-gnu-gcc -march=rv64gcv -c 1.c -O3 Below is just the bottom of stack obtained by gdb. There's an infinite recursion somewhere around `riscv_vector::avl_info::operator==`. #629078 0x0000000000fa3372 in riscv_vector::avl_info::operator==(riscv_vector::avl_info const&) const () #629079 0x0000000000fa37f9 in ?? () #629080 0x0000000000fa2543 in ?? () #629081 0x0000000000fa3372 in riscv_vector::avl_info::operator==(riscv_vector::avl_info const&) const () #629082 0x0000000000fa37f9 in ?? () #629083 0x0000000000fa2543 in ?? () #629084 0x0000000000fa3372 in riscv_vector::avl_info::operator==(riscv_vector::avl_info const&) const () #629085 0x0000000000fa37f9 in ?? () #629086 0x0000000000fa2543 in ?? () #629087 0x0000000000fa3372 in riscv_vector::avl_info::operator==(riscv_vector::avl_info const&) const () #629088 0x0000000000fa37f9 in ?? () #629089 0x0000000000fa2543 in ?? () #629090 0x0000000000fa3372 in riscv_vector::avl_info::operator==(riscv_vector::avl_info const&) const () #629091 0x0000000000fa394b in ?? () #629092 0x0000000000f9f588 in riscv_vector::vector_insn_info::compatible_p(riscv_vector::vector_insn_info const&) const () #629093 0x0000000000fa0eb9 in pass_vsetvl::compute_local_backward_infos(rtl_ssa::bb_info const*) () #629094 0x0000000000fa8c6b in pass_vsetvl::lazy_vsetvl() () #629095 0x0000000000fa8e1f in pass_vsetvl::execute(function*) () #629096 0x0000000000b5e21b in execute_one_pass(opt_pass*) () #629097 0x0000000000b5eac0 in ?? () #629098 0x0000000000b5ead2 in ?? () #629099 0x0000000000b5ead2 in ?? () #629100 0x0000000000b5eaf9 in execute_pass_list(function*, opt_pass*) () #629101 0x0000000000822588 in cgraph_node::expand() () #629102 0x0000000000823afb in ?? () #629103 0x0000000000825fd8 in symbol_table::finalize_compilation_unit() () #629104 0x0000000000c29bad in ?? () #629105 0x00000000006a4c97 in toplev::main(int, char**) () #629106 0x00000000006a6a8b in main ()
next prev parent reply other threads:[~2024-03-29 2:05 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-29 15:55 [Bug target/114172] New: " vogelm at buerokommunikation dot fernuni-hagen.de 2024-03-04 10:50 ` [Bug target/114172] [13 only] " bruce at hoult dot org 2024-03-29 2:05 ` wojciech_mula at poczta dot onet.pl [this message] 2024-04-24 13:13 ` [Bug target/114172] [13 only] RISC-V: " cvs-commit at gcc dot gnu.org 2024-04-24 13:19 ` kito 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-114172-4-hs3mF3eLk9@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).