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

            Bug ID: 123089
           Summary: [x86] Excessive run time with -march=znver3
           Product: gcc
           Version: 16.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dcb314 at hotmail dot com
  Target Milestone: ---

Created attachment 63033
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=63033&action=edit
C source code

For the attached code with recent gcc trunk:

foundBugs $ ../results/bin/gcc  bug1158.c -w -o bug1158.exe
foundBugs $ (ulimit -t 10; ./bug1158.exe)
checksum = 34099839
foundBugs $ ../results/bin/gcc  -O2 bug1158.c -w -o bug1158.exe
foundBugs $ (ulimit -t 10; ./bug1158.exe)
checksum = 34099839
foundBugs $ ../results/bin/gcc  -O3 bug1158.c -w -o bug1158.exe
foundBugs $ (ulimit -t 10; ./bug1158.exe)
checksum = 34099839
foundBugs $ ../results/bin/gcc  -O3 -fno-strict-aliasing bug1158.c -w -o
bug1158.exe
foundBugs $ (ulimit -t 10; ./bug1158.exe)
checksum = 34099839
foundBugs $ ../results/bin/gcc  -O3 -fno-strict-aliasing -march=znver3
bug1158.c -w -o bug1158.exe
foundBugs $ (ulimit -t 10; ./bug1158.exe)
Killed
foundBugs $ 

For compiler

foundBugs $ ../results/bin/gcc -v
Using built-in specs.
COLLECT_GCC=../results/bin/gcc
COLLECT_LTO_WRAPPER=/home/dcb42/gcc/results.20251209.asan.ubsan/libexec/gcc/x86_64-pc-linux-gnu/16.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../trunk/configure
--prefix=/home/dcb42/gcc/results.20251209.asan.ubsan --disable-bootstrap
--disable-doc --disable-multilib --with-build-config='bootstrap-asan
bootstrap-ubsan' --with-pkgversion=1dd44ebd5facfc96 --with-isl
--enable-checking=df,extra,fold,rtl,yes --enable-languages=c,c++,fortran
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 16.0.0 20251209 (experimental) (1dd44ebd5facfc96) 
foundBugs $ 

The bug first seems to occur sometime between g:55049da531f52464
and g:6ae7f781322d2813

Reply via email to