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/114551] [14 Regression] wrong code at -O3 on x86_64-linux-gnu since r14-2944
Date: Tue, 02 Apr 2024 23:43:39 +0000	[thread overview]
Message-ID: <bug-114551-4-9OpceaIFMZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114551-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
The first major difference with/without continue is the moving of `f >
(2147483647 - a)` checkout of the loop via lim2 in the case of not having the
continue.

You can replace the inner most loop with:
```
    for (; c < 4; c++) {
      [[unlikely]];
      d = f && a > 0 && f > (2147483647 - a) ? 0 : b[f];
    }
```

Also so yes it is the continue predictor that is coming into play.

  parent reply	other threads:[~2024-04-02 23:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-01 19:31 [Bug tree-optimization/114551] New: wrong code at -O3 on x86_64-linux-gnu zhendong.su at inf dot ethz.ch
2024-04-01 20:45 ` [Bug tree-optimization/114551] [14 Regression] " pinskia at gcc dot gnu.org
2024-04-02 11:33 ` rguenth at gcc dot gnu.org
2024-04-02 13:22 ` jakub at gcc dot gnu.org
2024-04-02 23:43 ` pinskia at gcc dot gnu.org [this message]
2024-04-03  3:44 ` [Bug tree-optimization/114551] [14 Regression] wrong code at -O3 on x86_64-linux-gnu since r14-2944 pinskia at gcc dot gnu.org
2024-04-03  3:46 ` pinskia at gcc dot gnu.org
2024-04-03 12:27 ` rguenth at gcc dot gnu.org
2024-04-04  7:00 ` cvs-commit at gcc dot gnu.org
2024-04-04  7:01 ` [Bug tree-optimization/114551] [13 " rguenth at gcc dot gnu.org
2024-05-06 12:06 ` [Bug tree-optimization/114551] [14 " rguenth 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-114551-4-9OpceaIFMZ@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).