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/110582] [14 Regression] Wrong code at -O2/3 on x86_64-linux-gnu
Date: Sat, 08 Jul 2023 01:17:20 +0000	[thread overview]
Message-ID: <bug-110582-4-Kkp14RabT9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110582-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Another testcase:
```
int a, b;
int main() {
  char a = 0;
  int t = 0;
  for (; t <253; t ++){
    int d = 2;
    d ^= 2 && a;
    b = a == 0 ? d : d / a;
    a = b;
  }
  for (; (1 + 95 << 24) + b + 1 + 686658714L + b - 2297271457;)
    ;
}
```

Just to show that you could count up from 0 to 253 and still have an issue
without any wrapping happening in the original code.

  parent reply	other threads:[~2023-07-08  1:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-07  8:03 [Bug c/110582] New: " shaohua.li at inf dot ethz.ch
2023-07-07  8:40 ` [Bug tree-optimization/110582] [14 Regression] " pinskia at gcc dot gnu.org
2023-07-07 11:19 ` rguenth at gcc dot gnu.org
2023-07-08  1:08 ` pinskia at gcc dot gnu.org
2023-07-08  1:17 ` pinskia at gcc dot gnu.org [this message]
2023-07-30 14:46 ` shaohua.li at inf dot ethz.ch
2023-07-31 16:06 ` cvs-commit at gcc dot gnu.org
2023-07-31 16:11 ` amacleod at redhat dot com

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-110582-4-Kkp14RabT9@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).