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

            Bug ID: 113296
           Summary: SPEC 2006 434.zeusmp segfaults on Aarch64 when built
                    with -Ofast -march=native -flto
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jamborm at gcc dot gnu.org
            Blocks: 26163
  Target Milestone: ---
              Host: aarch64-linux
            Target: aarch64-linux

Our Aarch64 benchmarker (armv8.2-a+crypto+fp16+rcpc+dotprod+ssbs)
signals that SPEC 2006 434.zeusmp segfaults at run-time when built
with -Ofast -march=native -flto and master revision
r14-7022-g34d339bbd0c1f5.


Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

Backtrace for this error:
#0  0x40000002978f in ???
#1  0x403ff0 in ggen_
        at
/home/gcc/buildworker/source/cpu2006/benchspec/CPU2006/434.zeusmp/build/build_peak_amd64-m64-mine.0000/ggen.f:762
#2  0x407a0f in setup_
        at
/home/gcc/buildworker/source/cpu2006/benchspec/CPU2006/434.zeusmp/build/build_peak_amd64-m64-mine.0000/setup.f:1135
#3  0x40fc3b in mstart_
        at
/home/gcc/buildworker/source/cpu2006/benchspec/CPU2006/434.zeusmp/build/build_peak_amd64-m64-mine.0000/mstart.f:301
#4  0x425ee3 in zeusmp
        at
/home/gcc/buildworker/source/cpu2006/benchspec/CPU2006/434.zeusmp/build/build_peak_amd64-m64-mine.0000/zeusmp.fppized.f:620
#5  0x400d5f in main
        at
/home/gcc/buildworker/source/cpu2006/benchspec/CPU2006/434.zeusmp/build/build_peak_amd64-m64-mine.0000/zeusmp.fppized.f:769


Unfortunately at the moment don't have another access to another
adequate Aarch64 machine to debug further and so I cannot provide more
information (and so the component "target" is likely bogus, sorry).


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163
[Bug 26163] [meta-bug] missed optimization in SPEC (2k17, 2k and 2k6 and 95)

Reply via email to