www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.bugs - [Issue 24254] New: LDC crash on Epyc Bergamo

https://issues.dlang.org/show_bug.cgi?id=24254

          Issue ID: 24254
           Summary: LDC crash on Epyc Bergamo
           Product: D
           Version: D2
          Hardware: x86_64
                OS: Linux
            Status: NEW
          Severity: major
          Priority: P1
         Component: dmd
          Assignee: nobody puremagic.com
          Reporter: jurij.pecar embl.de

Trying to figure out why Sambamba is crashing on Bergamo I noticed that issue
is already present with LDC. Just trying to start it results in a stack trace:

LDC 1.24 binary build:


ldc2[0x33f03d4]
Floating point exception (core dumped)

LDC 1.35 built from source with Easybuild, LLVM 16.0.6, GCC 12.3



(/g/easybuild/x86_64/Rocky/8/genoa/software/LLVM/16.0.6-GCCcore-12.3.0/lib/libLLVM-16.so+0x918bbe)



(/g/easybuild/x86_64/Rocky/8/znver4/software/LDC/1.35.0-GCCcore-12.3.0/bin/ldc2+0xc82ac4)

(/g/easybuild/x86_64/Rocky/8/znver4/software/LDC/1.35.0-GCCcore-12.3.0/bin/ldc2+0xc82c09)

_D2rt5minfo13rt_moduleCtorUZ14__foreachbody1MFKSQBu19sections_elf_shared3DSOZi
(/g/easybuild/x86_64/Rocky/8/znver4/software/LDC/1.35.0-GCCcore-12.3.0/bin/ldc2+0xc9cbc9)

(/g/easybuild/x86_64/Rocky/8/znver4/software/LDC/1.35.0-GCCcore-12.3.0/bin/ldc2+0xc9db6a)

(/g/easybuild/x86_64/Rocky/8/znver4/software/LDC/1.35.0-GCCcore-12.3.0/bin/ldc2+0xc93428)

(/g/easybuild/x86_64/Rocky/8/znver4/software/LDC/1.35.0-GCCcore-12.3.0/bin/ldc2+0xc939ad)

(/g/easybuild/x86_64/Rocky/8/znver4/software/LDC/1.35.0-GCCcore-12.3.0/bin/ldc2+0xc93808)

(/g/easybuild/x86_64/Rocky/8/znver4/software/LDC/1.35.0-GCCcore-12.3.0/bin/ldc2+0xc9365e)

(/g/easybuild/x86_64/Rocky/8/znver4/software/LDC/1.35.0-GCCcore-12.3.0/bin/ldc2+0x797e4d)


(/g/easybuild/x86_64/Rocky/8/znver4/software/LDC/1.35.0-GCCcore-12.3.0/bin/ldc2+0x79a12e)


Can't run binary release 1.35 as it requires glibc 2.29 (el8 only has 2.28).

Does this stack trace ring any bells? Otherwise please let me know what further
info would be useful to provide in order to fix this issue. It might be that
root cause is further still, in llvm.

Thanks,

--
Nov 21 2023