public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jwzeng at nuaa dot edu.cn" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/112344] [14 Regression] Wrong code at -O2 on x86_64-pc-linux-gnu
Date: Thu, 02 Nov 2023 06:47:45 +0000	[thread overview]
Message-ID: <bug-112344-4-P8YSDRsYQK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112344-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Junwei Zeng <jwzeng at nuaa dot edu.cn> ---
(In reply to Andrew Pinski from comment #2)
> Corrected testcase:
> ```
> int printf(const char *, ...);
> void a() {
>   long b = 2036854775807;
>   char c = 3;
>   short d;
>   int e = -2147483648, f = 0;
>   for (; f < 7; f++)
>     while (e < 20) {
>       e += 2;
>       d = c -= b;
>     }
>   printf("%d\n", d);
> }
> int main() { a(); }
> ```

Sorry, I copied the wrong test case, the correct test case is the one in
Compiler explorer, which is the one you mentioned.

Compiler explorer: https://godbolt.org/z/8hq64asT5

  parent reply	other threads:[~2023-11-02  6:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-02  6:30 [Bug middle-end/112344] New: " jwzeng at nuaa dot edu.cn
2023-11-02  6:41 ` [Bug middle-end/112344] " pinskia at gcc dot gnu.org
2023-11-02  6:42 ` pinskia at gcc dot gnu.org
2023-11-02  6:47 ` jwzeng at nuaa dot edu.cn [this message]
2023-11-02  6:49 ` pinskia at gcc dot gnu.org
2023-11-02 10:06 ` rguenth at gcc dot gnu.org
2023-11-21 19:22 ` jakub at gcc dot gnu.org
2023-11-21 19:23 ` jakub at gcc dot gnu.org
2023-11-22  7:43 ` rguenth at gcc dot gnu.org
2023-11-22  9:10 ` rguenth at gcc dot gnu.org
2023-11-22 10:06 ` rguenth at gcc dot gnu.org
2023-11-22 14:40 ` cvs-commit at gcc dot gnu.org
2023-11-22 14:41 ` rguenth at gcc dot gnu.org
2023-11-24  7:50 ` cvs-commit at gcc dot gnu.org
2024-02-18 10:07 ` cvs-commit 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-112344-4-P8YSDRsYQK@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).