public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/109524] [13 Regression] ICE: SIGSEGV in remove_unreachable::remove_and_update_globals (tree-vrp.cc:136) with -O3 -fno-tree-forwprop -fnon-call-exceptions -fno-tree-ccp -fno-tree-fre Date: Sat, 15 Apr 2023 22:49:10 +0000 [thread overview] Message-ID: <bug-109524-4-jnSxfI4pBY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109524-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109524 --- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> --- The edge in question has been removed in #2 0x00000000025b0e32 in free_edge (fn=0x7fffea2ed7e8, e=<error reading variable: Cannot access memory at address 0xa5a5a5a5a5a5a5f9>) at ../../gcc/cfg.cc:93 #3 0x00000000025b1631 in remove_edge_raw (e=<error reading variable: Cannot access memory at address 0xa5a5a5a5a5a5a5f9>) at ../../gcc/cfg.cc:367 #4 0x00000000009e447c in remove_edge (e=<error reading variable: Cannot access memory at address 0xa5a5a5a5a5a5a5f9>) at ../../gcc/cfghooks.cc:464 #5 0x00000000009e49b5 in delete_basic_block (bb=<basic_block 0x7fffea30c240 (8)>) at ../../gcc/cfghooks.cc:636 #6 0x000000000112b193 in remove_edge_and_dominated_blocks (e=<edge 0x7fffea30b600 (3 -> 6)>) at ../../gcc/tree-cfg.cc:8958 #7 0x000000000112b34f in gimple_purge_dead_eh_edges (bb=<basic_block 0x7fffea2dbea0 (3)>) at ../../gcc/tree-cfg.cc:9002 #8 0x000000000112b412 in gimple_purge_all_dead_eh_edges (blocks=0x39d0cb8) at ../../gcc/tree-cfg.cc:9029 #9 0x000000000131281a in substitute_and_fold_engine::substitute_and_fold (this=0x7fffffffd960, block=<basic_block 0x0>) at ../../gcc/tree-ssa-propagate.cc:998 #10 0x000000000145ef6b in execute_ranger_vrp (fun=0x7fffea2ed7e8, warn_array_bounds_p=true, final_p=false) at ../../gcc/tree-vrp.cc:1102 and #0 0x00000000009d9c1b in bb_seq_addr (bb=<error reading variable: Cannot access memory at address 0xa5a5a5a5a5a5a5f9>) at ../../gcc/gimple.h:1820 #1 0x00000000009f7325 in gsi_last_bb (bb=<error reading variable: Cannot access memory at address 0xa5a5a5a5a5a5a5f9>) at ../../gcc/gimple-iterator.h:160 #2 0x0000000000c7fe17 in gsi_last_nondebug_bb (bb=<error reading variable: Cannot access memory at address 0xa5a5a5a5a5a5a5f9>) at ../../gcc/gimple-iterator.h:321 #3 0x000000000265dca9 in gimple_outgoing_range_stmt_p (bb=<error reading variable: Cannot access memory at address 0xa5a5a5a5a5a5a5f9>) at ../../gcc/gimple-range-edge.cc:42 #4 0x000000000145b54d in remove_unreachable::remove_and_update_globals (this=0x7fffffffd970, final_p=false) at ../../gcc/tree-vrp.cc:136 #5 0x000000000145ef87 in execute_ranger_vrp (fun=0x7fffea2ed7e8, warn_array_bounds_p=true, final_p=false) at ../../gcc/tree-vrp.cc:1104 then tries to access the already freed edge which was kept in some list of edges across the gimple_purge_all_dead_eh_edges.
next prev parent reply other threads:[~2023-04-15 22:49 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-15 10:27 [Bug tree-optimization/109524] New: " zsojka at seznam dot cz 2023-04-15 19:50 ` [Bug tree-optimization/109524] " pinskia at gcc dot gnu.org 2023-04-15 20:17 ` pinskia at gcc dot gnu.org 2023-04-15 20:18 ` pinskia at gcc dot gnu.org 2023-04-15 20:33 ` jakub at gcc dot gnu.org 2023-04-15 20:38 ` pinskia at gcc dot gnu.org 2023-04-15 20:55 ` jakub at gcc dot gnu.org 2023-04-15 21:12 ` pinskia at gcc dot gnu.org 2023-04-15 22:49 ` jakub at gcc dot gnu.org [this message] 2023-04-15 23:00 ` jakub at gcc dot gnu.org 2023-04-17 7:22 ` rguenth at gcc dot gnu.org 2023-04-17 9:03 ` cvs-commit at gcc dot gnu.org 2023-04-17 9:04 ` rguenth at gcc dot gnu.org 2023-04-19 8:04 ` cvs-commit at gcc dot gnu.org 2023-04-19 8:09 ` cvs-commit 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-109524-4-jnSxfI4pBY@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).