public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/107570] [13 Regression] ICE: Segmentation fault (in instantiate_scev_name/gimple_bb) Date: Tue, 08 Nov 2022 15:11:31 +0000 [thread overview] Message-ID: <bug-107570-4-m9yBb0gToV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107570-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107570 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2022-11-08 Priority|P3 |P1 Target Milestone|--- |13.0 Ever confirmed|0 |1 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- #1 0x000000000167403c in instantiate_scev_name ( instantiate_below=<edge 0x7ffff66ea330 (3 -> 7)>, evolution_loop=0x7ffff651a848, inner_loop=0x7ffff651a848, chrec= <ssa_name 0x7ffff6522f30 2>, fold_conversions=0x0, size_expr=2) at /home/rguenther/src/trunk/gcc/tree-scalar-evolution.cc:2270 2270 basic_block def_bb = gimple_bb (SSA_NAME_DEF_STMT (chrec)); (gdb) p chrec $1 = <ssa_name 0x7ffff6522f30 2> (gdb) p debug_tree (chrec) <ssa_name 0x7ffff6522f30 type <error_mark 0x7ffff6517d80> nothrow def_stmt version:2 in-free-list> $2 = void and we release the SSA name via #0 release_ssa_name_fn (fn=0x7ffff66e9000, var=<ssa_name 0x7ffff6522f30 2>) at /home/rguenther/src/trunk/gcc/tree-ssanames.cc:555 #1 0x000000000187eeae in release_ssa_name (name=<ssa_name 0x7ffff6522f30 2>) at /home/rguenther/src/trunk/gcc/tree-ssanames.h:123 #2 0x0000000001881c24 in release_defs (stmt=<gimple_assign 0x7ffff66d1730>) at /home/rguenther/src/trunk/gcc/tree-ssanames.cc:832 #3 0x00000000017bd61c in substitute_and_fold_engine::substitute_and_fold ( this=0x7fffffffda00, block=<basic_block 0x0>) at /home/rguenther/src/trunk/gcc/tree-ssa-propagate.cc:1009 #4 0x000000000193e886 in execute_ranger_vrp (fun=0x7ffff66e9000, warn_array_bounds_p=false, final_p=true) at /home/rguenther/src/trunk/gcc/tree-vrp.cc:4543 #5 0x000000000193ebde in (anonymous namespace)::pass_vrp::execute ( this=0x43b16f0, fun=0x7ffff66e9000) at /home/rguenther/src/trunk/gcc/tree-vrp.cc:4628 #6 0x00000000013b2c9d in execute_one_pass ( pass=<opt_pass* 0x43b16f0 "vrp"(204)>) at /home/rguenther/src/trunk/gcc/passes.cc:2644 releasing SSA names while still folding looks dangerous in case the folding eventually invokes SCEV which has a cache.
next prev parent reply other threads:[~2022-11-08 15:11 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-08 13:52 [Bug tree-optimization/107570] New: " asolokha at gmx dot com 2022-11-08 15:11 ` rguenth at gcc dot gnu.org [this message] 2022-11-21 12:12 ` [Bug tree-optimization/107570] [13 Regression] ICE: Segmentation fault (in instantiate_scev_name/gimple_bb) since r13-3595-g7b1cdca6d6d594a8 marxin at gcc dot gnu.org 2023-02-01 17:56 ` jakub at gcc dot gnu.org 2023-02-01 18:12 ` amacleod at redhat dot com 2023-02-03 19:43 ` cvs-commit at gcc dot gnu.org 2023-02-03 19:43 ` amacleod at redhat dot com
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-107570-4-m9yBb0gToV@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).