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 middle-end/111290] [11/12/13/14 Regression] Wrong code at -O0 on x86_64-pc-linux-gnu
Date: Tue, 05 Sep 2023 06:49:32 +0000	[thread overview]
Message-ID: <bug-111290-4-fp3niVu8EQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111290-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
```
int main()
{
        int t = c;
        c |= d / a;
    b = (c) >= ((e %= 0x6B1D8456) > (res ^= t));
    printf("%d\n", res);
}
```
gives -104
While:
```
int main()
{
        c |= d / a;
        int t = c;
    b = (c) >= ((e %= 0x6B1D8456) > (res ^= t));
    printf("%d\n", res);
}
```

Gives -112 
Both are valid way of representing the original code as there is no sequence
point between them.

Note C++11 makes this well defined.

      parent reply	other threads:[~2023-09-05  6:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-05  6:20 [Bug middle-end/111290] New: " jwzeng at nuaa dot edu.cn
2023-09-05  6:45 ` [Bug middle-end/111290] " pinskia at gcc dot gnu.org
2023-09-05  6:49 ` pinskia at gcc dot gnu.org [this message]

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-111290-4-fp3niVu8EQ@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).