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/109778] [12/13/14 Regression] Wrong code at -O1 and above on x86_64-linux-gnu since GCC-12.2
Date: Mon, 08 May 2023 19:30:38 +0000	[thread overview]
Message-ID: <bug-109778-4-sVNb68O2QE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109778-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2023-05-08
     Ever confirmed|0                           |1
           Keywords|                            |wrong-code
          Component|c                           |tree-optimization
             Status|UNCONFIRMED                 |NEW
            Summary|Wrong code at -O3 on        |[12/13/14 Regression] Wrong
                   |x86_64-linux-gnu since      |code at -O1 and above on
                   |GCC-12.2                    |x86_64-linux-gnu since
                   |                            |GCC-12.2

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
ccp2:
Visiting statement:
_16 = (unsigned intD.9) g_15;
which is likely CONSTANT
Lattice value changed to CONSTANT 0xdb (0x20).  Adding SSA edges to worklist.
marking stmt to be not simulated again

Visiting statement:
_17 = _16 + 4294967210;
which is likely CONSTANT
Lattice value changed to CONSTANT 0x85 (0x20).  Adding SSA edges to worklist.
marking stmt to be not simulated again

Visiting statement:
_18 = _17 <= 7;
which is likely CONSTANT
Lattice value changed to CONSTANT 0.  Adding SSA edges to worklist.
marking stmt to be not simulated again


Note this is with -O1 with:
```

int printf(const char *, ...);
int a, b, c, d;
int *e = &c;
static inline unsigned f(unsigned char g) {
  g = 1 | g << 1;
  g = g >> 4 | g << 4;
  return g;
}
static inline void h(unsigned g) { *e = 8 > f(g + 86) - 86; }
int main() {
  d = a && b;
  h(d + 4);
  printf("%d\n", c);
}
```

  reply	other threads:[~2023-05-08 19:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-08 19:18 [Bug c/109778] New: Wrong code at -O3 " shaohua.li at inf dot ethz.ch
2023-05-08 19:30 ` pinskia at gcc dot gnu.org [this message]
2023-05-08 19:31 ` [Bug tree-optimization/109778] [13/14 Regression] Wrong code at -O1 and above on x86_64-linux-gnu pinskia at gcc dot gnu.org
2023-05-08 19:36 ` jakub at gcc dot gnu.org
2023-05-08 22:09 ` jakub at gcc dot gnu.org
2023-05-09  7:38 ` rguenth at gcc dot gnu.org
2023-05-09 10:11 ` cvs-commit at gcc dot gnu.org
2023-05-09 10:19 ` cvs-commit at gcc dot gnu.org
2023-05-09 10:23 ` [Bug tree-optimization/109778] [10/11/12/13 " jakub at gcc dot gnu.org
2023-05-09 10:49 ` cvs-commit at gcc dot gnu.org
2023-05-09 10:49 ` cvs-commit at gcc dot gnu.org
2023-05-09 10:56 ` cvs-commit at gcc dot gnu.org
2023-05-09 10:56 ` cvs-commit at gcc dot gnu.org
2023-05-09 11:04 ` cvs-commit at gcc dot gnu.org
2023-05-09 11:04 ` cvs-commit at gcc dot gnu.org
2023-05-09 11:10 ` cvs-commit at gcc dot gnu.org
2023-05-09 11:10 ` cvs-commit at gcc dot gnu.org
2023-05-21 16:56 ` jakub 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-109778-4-sVNb68O2QE@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).