[Bug target/109780] csmith: runtime crash with -O2 -march=znver1

2023-05-09 Thread amonakov at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109780

--- Comment #12 from Alexander Monakov  ---
Eh, that commit sneakily changed avx2 tuning without explaining that in the
Changelog. Anyway, it should possible to "workaround" that by compiling with

  -O2 -mavx2 -mtune=skylake-avx512

instead, in which case the bisect will likely point to commit 
r12-2666-g29f0e955c97 ("x86: Update piecewise move and store") (before that,
expansion of memcpy via store-by-pieces wouldn't use avx2).

Also, PR 109093 looks very related.

[Bug target/109780] csmith: runtime crash with -O2 -march=znver1

2023-05-09 Thread marxin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109780

--- Comment #11 from Martin Liška  ---
(In reply to Alexander Monakov from comment #10)
> (In reply to Martin Liška from comment #9)
> > Started with zen tuning revision r13-4839-geef81eefcdc2a5.
> 
> The issue is also reproducible with -march=haswell or -march=skylake, so you
> can use those for further bisection.

With -march=skylake it began with r13-4124-g156f523f9582f1 and with
-march=haswell it started with the very same revision.

[Bug target/109780] csmith: runtime crash with -O2 -march=znver1

2023-05-09 Thread amonakov at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109780

--- Comment #10 from Alexander Monakov  ---
(In reply to Martin Liška from comment #9)
> Started with zen tuning revision r13-4839-geef81eefcdc2a5.

The issue is also reproducible with -march=haswell or -march=skylake, so you
can use those for further bisection.

[Bug target/109780] csmith: runtime crash with -O2 -march=znver1

2023-05-09 Thread marxin at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109780

Martin Liška  changed:

   What|Removed |Added

 CC||marxin at gcc dot gnu.org

--- Comment #9 from Martin Liška  ---
Started with zen tuning revision r13-4839-geef81eefcdc2a5.

[Bug target/109780] csmith: runtime crash with -O2 -march=znver1

2023-05-09 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109780

--- Comment #8 from David Binderman  ---
As far as the snapshots go, 20221218..20221225 seems to be the range.

In git, this is g:fd69977febf399d1992bbf8d66ae9170e0a4dc9f ..
g:febb58d28bfa4b544ec7ffec2d61f46d25205ff0, which is 123 commits.

Trying g:89ba8366fe12fd2d04535c99ba67f33d7e305132.

[Bug target/109780] csmith: runtime crash with -O2 -march=znver1

2023-05-09 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109780

--- Comment #7 from David Binderman  ---
(In reply to David Binderman from comment #6)
> Broken at 20230205, so range is now [20221106.. 20230205].
> 
> Trying snapshot 20221218

That was good, so range is 20221218..20230108.

Trying snapshot 20230101.

[Bug target/109780] csmith: runtime crash with -O2 -march=znver1

2023-05-09 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109780

--- Comment #6 from David Binderman  ---
Broken at 20230205, so range is now [20221106.. 20230205].

Trying snapshot 20221218

[Bug target/109780] csmith: runtime crash with -O2 -march=znver1

2023-05-09 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109780

--- Comment #5 from David Binderman  ---
Seems good at date 20221106, so the date range is [20221106..20230417].

Trying 20230205.

[Bug target/109780] csmith: runtime crash with -O2 -march=znver1

2023-05-09 Thread dcb314 at hotmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109780

--- Comment #4 from David Binderman  ---
Seems good with g:18547874ee205d83 dated 20220515 and bad with
g:73f7109ffb159302,
dated yesterday.

[Bug target/109780] csmith: runtime crash with -O2 -march=znver1

2023-05-09 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109780

Richard Biener  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
   Keywords||needs-bisection
 Target||x86_64-*-*
Version|unknown |14.0
   Last reconfirmed||2023-05-09
 Ever confirmed|0   |1

[Bug target/109780] csmith: runtime crash with -O2 -march=znver1

2023-05-08 Thread amonakov at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109780

Alexander Monakov  changed:

   What|Removed |Added

 CC||amonakov at gcc dot gnu.org

--- Comment #3 from Alexander Monakov  ---
Works with -fstack-reuse=none. Somehow GCC is confused about stack layout in
func_36. It leaves rsp misaligned by 8 mod 16, but computes the base of l_814
for
__builtin_memset (_814, 0, 80) as if rsp is aligned mod 16.

[Bug target/109780] csmith: runtime crash with -O2 -march=znver1

2023-05-08 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109780

--- Comment #2 from Andrew Pinski  ---
I should mention there is no difference in the gimple dump between with and
without -march=znver1 .

[Bug target/109780] csmith: runtime crash with -O2 -march=znver1

2023-05-08 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109780

Andrew Pinski  changed:

   What|Removed |Added

  Component|middle-end  |target

--- Comment #1 from Andrew Pinski  ---
=> 0x00402378 :vmovdqa %xmm3,(%r8)
   0x0040237d :vmovdqa %xmm2,0x10(%r8)
   0x00402383 :neg%r9
   0x00402386 :vmovdqa %xmm2,0x20(%r8)
End of assembler dump.
(gdb) p $r8
$1 = 140737488346408
(gdb) p/x $r8
$2 = 0x7fffdd28