- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have just installed oneAPI 2024.1.0 and, while compiling and linking the debug configuration of my application, I am getting the warning copied to the subject of this post.
How should I understand the warning, taking into account that the option /check:uninit can be enabled in Fortran -> Run-time settings in Visual Studio?
I tried searching for this problem and I could see it has been present in previous versions of oneAPI and that it might have something in common with MKL which my application uses.
I use oneAPI Base+HPC 2024.1.0 in Visual Studio 2022 Pro on Windows 10 Pro, my application is in Fortran and I use the ifx compiler.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This is a restriction of ifx specifically - it uses a different technique for uninitialized variable detection that is not (yet?) provided for Windows compilers. I hope that this is a temporary omission. It has nothing to do with MKL. You could switch to ifort for now if you wanted that feature, though it is much less capable than the one ifx can use on Linux.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I wonder when checking uninitialised variables will be restored for Windows users, especially with the imminent removal of ifort deployment.
Seems to me that removing ifort is premature

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