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 tree-optimization/20514] hoisting of label out of jumptable would take place at cse, should happen at trees
Date: Sat, 05 Aug 2023 03:09:54 +0000	[thread overview]
Message-ID: <bug-20514-4-zwuk6ZoEME@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-20514-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
in GCC 13+ we get now (for the testcase in comment #0) at -O3:
```
  <bb 4> [local count: 452984831]:
  # i_lsm.4_2 = PHI <i_lsm.4_11(3), 4(4)>
  if (i_lsm.4_2 == 5)
    goto <bb 4>; [25.00%]
  else
    goto <bb 5>; [75.00%]

  <bb 5> [local count: 452984832]:
  goto <bb 5>; [100.00%]
```
This is an infinite no matter which branch is taken ...
Coming in we get either `3->4->4->5` or `3->4->5` no matter what we end up in 5
always.

  parent reply	other threads:[~2023-08-05  3:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-20514-4@http.gcc.gnu.org/bugzilla/>
2021-05-04 12:31 ` rguenth at gcc dot gnu.org
2021-07-24  5:17 ` pinskia at gcc dot gnu.org
2023-08-05  3:09 ` pinskia at gcc dot gnu.org [this message]
     [not found] <bug-20514-334@http.gcc.gnu.org/bugzilla/>
2006-09-17  8:00 ` pinskia at gcc dot gnu dot org
2007-12-14 15:01 ` aldot at gcc dot gnu dot org
2005-03-17  8:21 [Bug tree-optimization/20514] New: " aoliva at gcc dot gnu dot org
2005-03-17 17:23 ` [Bug tree-optimization/20514] " pinskia at gcc dot gnu dot org
2005-04-13 18:30 ` pinskia at gcc dot gnu dot org
2005-05-06  8:50 ` steven at gcc dot gnu dot org
2005-05-06 13:40 ` pinskia at gcc dot gnu dot 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-20514-4-zwuk6ZoEME@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).