Has anyone had ld crash using ifx 2025.1.1 and LTO in pass 17

[Mark_Lewy]

Before I go any further trying to isolate this, has anyone seen this?  Using ifx 2025.1.1 on Linux (Ubuntu 22.04.5 LTS under WSL) one of our shared libraries causes ld to crash:

[100%] Linking Fortran shared library out/lib/libsimlib2d.so
ifx: error #10105: ld: core dumped
ifx: warning #10102: unknown signal(204369936)
ifx: error #10106: Fatal error in ld, terminated by unknown
gmake[3]: *** [CMakeFiles/simlib2d.dir/build.make:1330: out/lib/libsimlib2d.so] Error 1
gmake[3]: *** Deleting file 'out/lib/libsimlib2d.so'
gmake[2]: *** [CMakeFiles/Makefile2:262: CMakeFiles/simlib2d.dir/all] Error 2
gmake[1]: *** [CMakeFiles/Makefile2:269: CMakeFiles/simlib2d.dir/rule] Error 2
gmake: *** [Makefile:176: simlib2d] Error 2

Using  "-mllvm -opt-bisect-limit=<pass>", I have isolated this to pass 17 (JumpThreadingPass).  I'm currently applying this option to all the source files in the library, I can go further and check selected files, if necessary.

This library links without LTO and on Windows (where it's a static library).

This library also links with ifx 2025.0.4 and 2024.2.1 on Linux.

[Mark_Lewy · Accepted solution]

I decided to take a look at this further by trying to selectively compile and link parts of the library.  To do this, I sorted its sources into build order and discovered a load of duplicates.  Upon removing those, the full library built and linked fine.  Go figure!

[Mark_Lewy]

I assume this is meant to be a reply to ifx linking memory issue - Intel Community?

Aside: assuming that 2025.2.0 is the last 2025.x release, we will probably be updating our products to use it for production; we generally use the last release of the year, as that remains supported for a while.

[Ron_Green]

@Mark_Lewy  <sigh> yes, it was supposed to be for that other thread.  sorry.  Yet another sign I need to retire.