[Bug tree-optimization/107194] New: wrong code at -O1 on x86_64-linux-gnu

[Bug tree-optimization/107194] New: wrong code at -O1 on x86_64-linux-gnu

[zhendong.su at inf dot ethz.ch]

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

            Bug ID: 107194
           Summary: wrong code at -O1 on x86_64-linux-gnu
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: zhendong.su at inf dot ethz.ch
  Target Milestone: ---

This works for 12.2, so should be a recent regression.

Compiler Explorer: https://godbolt.org/z/7vobTxhG4


[581] % gcctk -v
Using built-in specs.
COLLECT_GCC=gcctk
COLLECT_LTO_WRAPPER=/local/suz-local/software/local/gcc-trunk/libexec/gcc/x86_64-pc-linux-gnu/13.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../gcc-trunk/configure --disable-bootstrap
--enable-checking=yes --prefix=/local/suz-local/software/local/gcc-trunk
--enable-sanitizers --enable-languages=c,c++ --disable-werror --enable-multilib
--with-system-zlib
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 13.0.0 20221009 (experimental) [master r13-3180-ge95e91eccd0] (GCC) 
[582] % 
[582] % gcctk -O1 small.c
[583] % ./a.out
Aborted
[584] % cat small.c
int a, b;
int main() {
  int c = 0;
  long d;
  for (; b < 1; b++) {
    (c && d) & 3 || a;
    d = c;
    c = -1;
    if (d)
      __builtin_abort();
  }
  return 0;
}

[Bug tree-optimization/107194] [13 Regression] wrong code at -O1 on x86_64-linux-gnu

[rguenth at gcc dot gnu.org]

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
           Keywords|                            |needs-bisection, wrong-code
   Last reconfirmed|                            |2022-10-10
            Summary|wrong code at -O1 on        |[13 Regression] wrong code
                   |x86_64-linux-gnu            |at -O1 on x86_64-linux-gnu
     Ever confirmed|0                           |1
      Known to work|                            |12.2.0
            Version|unknown                     |13.0
   Target Milestone|---                         |13.0

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed.

[Bug tree-optimization/107194] [13 Regression] wrong code at -O1 on x86_64-linux-gnu since r13-3090-gdf4c584c567263fd

[marxin at gcc dot gnu.org]

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

Martin Liška <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |aldyh at gcc dot gnu.org,
                   |                            |marxin at gcc dot gnu.org
            Summary|[13 Regression] wrong code  |[13 Regression] wrong code
                   |at -O1 on x86_64-linux-gnu  |at -O1 on x86_64-linux-gnu
                   |                            |since
                   |                            |r13-3090-gdf4c584c567263fd

--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Started with r13-3090-gdf4c584c567263fd.

[Bug tree-optimization/107194] [13 Regression] wrong code at -O1 on x86_64-linux-gnu since r13-3090-gdf4c584c567263fd

[aldyh at gcc dot gnu.org]

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

Aldy Hernandez <aldyh at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |DUPLICATE
             Status|NEW                         |RESOLVED

--- Comment #3 from Aldy Hernandez <aldyh at gcc dot gnu.org> ---
This is the same issue as 107195.  I have added this testcase to my upcoming
patch.

*** This bug has been marked as a duplicate of bug 107195 ***