LLVM ERROR: out of memory with IFX 2025.2

[Mentzer__Stuart]

Our Windows IFX debug builds are failing after the update to oneAPI 2025.2 with
  LLVM ERROR: out of memory
errors that appear to happen during the link. System memory use was low on a 64 GB RAM system so this is not due to physical memory exhaustion.

The build command looks like this:
ifx /nologo /fpp /warn:all,nointerfaces,noexternals,notruncated_source /nogen-interfaces /align:zcommons,array64byte /assume:buffered_io,noold_unit_star /Qprotect-parens /fp:consistent /libs:dll /F0x1000000 /arch:CORE-AVX2 /Od /debug /Z7 /fpe:0 /check:all /Qfp-stack-check /Qinit:huge,snan,arrays /traceback /Qsave-temps- *.f90 libopenblas.lib

We found that removing /fpe:0 and /Qinit:snan prevents the error.

I cannot share the application where this is happening so this is an informational post for the community. If I can reproduce it with a small demo code I'll post that here later.

System info:

• Windows 11 with all updates.
• Intel 12th Gen CPU.
• 64 GB of RAM

[working]

Thanks for sharing this it’s really helpful! Sounds like a regression in the latest oneAPI version. Good catch on the workaround by removing /fpe:0 and /Qinit:snan. Hopefully Intel addresses this in the next update. Looking forward to your test case if you're able to share one.