Is there no runtime redistributales installer for 2025.2?

[dajum81]

I can't find it and the download page for the runtimes has not been updated since 2025.2 was released.  Does the 2025.1 runtime still work for 2025.2?

[Ron_Green]

I assume you are basing this on the contents of this page:

https://www.intel.com/content/www/us/en/developer/articles/tool/compilers-redistributable-libraries-by-version.html

I will ask the support team to update this page.

Will the 2025.1 Runtime work for 2025.2?  It depends.  It is certainly not recommended to use an older RTL with an newer compiler.  The opposite works fine, of course.  

You should consult the "New in ifx 2025.2.0" section in the Release Notes.  None of these new features will work since they require Runtime Library support.  For example, in 2025.2 we added F2023 SELECTED_LOGICAL_KIND intrinsic.  If you call that function in your code you will get an undefined intrinsic error.  But if your code is not using Fortran 2023 features or new OpenMP features you should be OK to use the older RTL. 

 

[dajum81]

Hi Ron,

It appears most of the pages are not updated to 2025.2

Intel® Fortran Compiler for oneAPI Release Notes 2025

Seems to only go to 2025.1.1, I'm wondering what version of Visual Studio is supported.  The page lists 17.12.4 for 2025.1.  Do I need a higher version to get it work correctly.  The debugger seems to be hopelessly broken in this version as I can't see most of the arrays in my code.  I have a case into support for the issue, but I need to know what is really supported and required to get it to work.

Thanks,

Dave

[Ron_Green]

In the Release Notes, the 2025.2 information is in the "Change History" at the top of this document.

Is this about the VS Debugger or about the Runtime Libaries?  Those are entirely 2 different things.

If this is about Debugging, you should upgrade immediately to 2025.2.0  This has all the latest VS support and fixes to the debugger.  The debugger works with the compiler, which emits debug information.  The debug emissions had fixes in 2025.2 and more coming in 2025.3.  That debug emission is then used by the Fortran Expression Evalutor (FEE) in concert with the VS Debugger.  The FEE and VS should work together as well.  So yes, VS has to be at a version that is supported by the FFE and the VS Integrations.   The VS version supported in 2025.2.0 is not listed where it should be, which is here.   I will contact the page owners to get this updated.  But for now, you should definitely be using the 2025.2.0 compiler if you care about debugging in VS.

Getting back to the Runtime Libraries:  You do know that these packages are only needed when you have created a .exe or .dll project that you want to share with people.  And these people do not have Intel Fortran installed.  THAT is when you need the Runtime Libraries.  You give them your .exe or .dll, they install JUST the Runtime Libraries, and then they can run your code without Visual Studio or the full Intel compiler. 

If you are developing and running on your own PC, you do not need the Runtime Libraries kit.  The compiler installation brings in the full set of Fortran Runtime Libraries.

[dajum81]

Hi Ron,

I do not see what VS version works in the Change History section of the Release Notes that are found on the web page.  You can't select 2025.2 as a version (the form only lists 2025.1), but there are some notes there for 2025.2, they are just incomplete.  It would be more helpful if you posted it here then I would know and not have to wait for the web pages to get updated.  The debugger does not work for me in 2025.2.  I submitted by first bug report in 2019 or so, and it finally got fixed in 2024.  Now it is broken again.  I submitted the same reproducers and it has been verified as a problem by the support team.  So I don't see how I can use 2025.2. 

But we have thousands of users of our code who do need to install the run time libraries.  So for them getting a working link is extremely helpful. 

Thanks,

Dave