- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The porting guidelines say this warning is issued for flags that are not (currently) planned to be supported by IFX (https://www.intel.com/content/www/us/en/developer/articles/guide/porting-guide-for-ifort-to-ifx.html). However, the IFX compiler options documentation lists it without any warnings. Should the IFX user remove this flag from the build scripts or keep it in the hope of future implementation? Thanks for any help from the IFX developers and others.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am not sure where you see that -ip may be supported. ifx -qnextgen-diag does show it will be removed (was removed).
-ip that we used with ifort and our IL0 backend is not supported in llvm. What they do support is "link time optimization" or "lto". This is both what we used to call -ip and -ipo combined. To get the inlining and additional vectorization and optimization you saw with ifort, replace "-ip" with "-qipo" or "-flto". So yes, remove -ip or substitute with the llvm option -qipo
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am not sure where you see that -ip may be supported. ifx -qnextgen-diag does show it will be removed (was removed).
-ip that we used with ifort and our IL0 backend is not supported in llvm. What they do support is "link time optimization" or "lto". This is both what we used to call -ip and -ipo combined. To get the inlining and additional vectorization and optimization you saw with ifort, replace "-ip" with "-qipo" or "-flto". So yes, remove -ip or substitute with the llvm option -qipo

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