- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
With ifx 2025.0.4 (current latest) on Windows if I compile with /Qipo neither lib nor xilib will build a static library. xilib warns "Tool use is limited for IL0 based targets" and then passes the command along to lib. lib, not surprisingly, sees the ipo object files as "invalid or corrupt". Adding /Qipo to the xilib command doesn't help and I can't find any xilib documentation of an option it expects.
I have the same issue with icx.
I'm happy to create a reproducer but it just requires compiling any valid code with /Qipo and then trying to put it in a static library with a command like:
xilib /Qipo /out:my.lib my.obj
Is there some simple secret sauce I'm missing or is this something broken with the LLVM toolchain?
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am guessing you need a LLVM tool, look in C:\Program Files (x86)\Intel\oneAPI\2025.0\bin\compiler there is a llvm-lib.exe maybe that is the thing....
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks, Andrew. That works to build the library. Then it seems you have to link with ld-link.exe. Is this documented anywhere?
The directory of these tools is not put in PATH by the environment setup scripts. This LLVM migration is far from seamless!
I have to test if /Qipo is even worth all this faffing about with ifx and icx.
Progress!?

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page