public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/109601] Useless branch not eliminated when writing to a union
Date: Sun, 23 Apr 2023 18:48:52 +0000	[thread overview]
Message-ID: <bug-109601-4-alqJ4bk5Dm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109601-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109601

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
jump2 (which is after RA) does this for aarch64:

Forwarding edge 2->3 to 5 failed.
verify found no changes in insn with uid = 11.
Edge 2->4 redirected to 5
scanning new insn with uid = 47.
Replacing insn 11 by jump 47
deleting insn with uid = 11.
deleting insn with uid = 38.
deleting block 3
deleting block 4
Removing jump 47.
deleting insn with uid = 47.
Merging block 5 into block 2...
changing bb of uid 43
changing bb of uid 44
  from 5 to 2
changing bb of uid 45
  from 5 to 2
Merged blocks 2 and 5.
Merged 2 and 5 without moving.

For x86_64 does not have this.

  reply	other threads:[~2023-04-23 18:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-23 18:26 [Bug target/109601] New: " 67 at mniip dot com
2023-04-23 18:48 ` pinskia at gcc dot gnu.org [this message]
2023-04-23 18:58 ` [Bug rtl-optimization/109601] " 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-109601-4-alqJ4bk5Dm@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: link
Be 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).