public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amacleod at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/108684] [13 Regression] ICE: verify_ssa failed Date: Tue, 07 Feb 2023 18:30:24 +0000 [thread overview] Message-ID: <bug-108684-4-t8TIiUmw5B@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108684-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108684 --- Comment #3 from Andrew Macleod <amacleod at redhat dot com> --- OK, its been a while. Why is there a VUSE on the return? this is the IL right from into-ssa: int f (int a) { int _4; <bb 2> : # .MEM_2 = VDEF <.MEM_1(D)> __asm__(" " : "=X" a_3 : : "memory"); if (a_3 != 0) goto <bb 3>; [INV] else goto <bb 4>; [INV] <bb 3> : _4 = 0; // predicted unlikely by early return (on trees) predictor. # VUSE <.MEM_2> return _4; <bb 4> : __builtin_unreachable (); } The problem is that in VRP, we change a_3's global range to be ~[0,0], rewrite the condition to remove the block with the builtin_unreachable... which there leaves the IL something like: <bb 2> [local count: 1073741824]: # .MEM_2 = VDEF <.MEM_1(D)> __asm__(" " : "=X" a_3 : : "memory"); <bb 3> [local count: 1073741824]: # VUSE <.MEM_2> return 0; and since there are no more uses of a_3, the asm is considered dead and removed by simple_dce_from_worklist. BUt it does not adjust the vdefs at all.. so we when its deleted, we are still eft with: <bb 3> [local count: 1073741824]: # VUSE <.MEM_2> return 0; but now there is no longer a definition of MEM_2 and verify_ssa fails. I can fix it by not trying to dce any defs that have VDEFS on them... but that doesnt seem like the correct long term solution... Why is there a VUSE on that return anyway? to keep it from being hoisted above the asm? Whats the correct thing to do here? Im surprised that somewhere in the stmt deletion process, it doesnt rewrite all uses of MEM_2 to MEM_1 before deliting it. Or is that a manual step?
next prev parent reply other threads:[~2023-02-07 18:30 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-06 18:49 [Bug c++/108684] New: " gscfq@t-online.de 2023-02-06 18:55 ` [Bug tree-optimization/108684] " pinskia at gcc dot gnu.org 2023-02-06 20:23 ` pinskia at gcc dot gnu.org 2023-02-06 20:26 ` pinskia at gcc dot gnu.org 2023-02-07 14:05 ` rguenth at gcc dot gnu.org 2023-02-07 18:30 ` amacleod at redhat dot com [this message] 2023-02-07 18:33 ` pinskia at gcc dot gnu.org 2023-02-07 18:37 ` [Bug tree-optimization/108684] [12/13 " pinskia at gcc dot gnu.org 2023-02-07 18:39 ` amacleod at redhat dot com 2023-02-07 18:45 ` pinskia at gcc dot gnu.org 2023-02-07 19:56 ` pinskia at gcc dot gnu.org 2023-02-07 19:59 ` jakub at gcc dot gnu.org 2023-02-07 20:03 ` pinskia at gcc dot gnu.org 2023-02-08 19:14 ` pinskia at gcc dot gnu.org 2023-02-09 15:23 ` pinskia at gcc dot gnu.org 2023-02-10 1:47 ` cvs-commit at gcc dot gnu.org 2023-02-10 1:48 ` [Bug tree-optimization/108684] [12 " pinskia at gcc dot gnu.org 2023-03-10 21:55 ` cvs-commit at gcc dot gnu.org 2023-03-10 21:55 ` pinskia at gcc dot gnu.org 2023-05-13 14:17 ` 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-108684-4-t8TIiUmw5B@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).