topic Steve, Colleagues, in Intel® Fortran Compiler

Problem with VS Release 15.8.0

David_DiLaura1 — Thu, 16 Aug 2018 21:18:07 GMT

Colleagues,

Is anyone (else) having problems with VS Release 15.8.0? One of our team installed that update this morning and now any attempt to display elements in an array variable in debug mode (hover with the mouse, click on the expand arrow) crashes VS -- brings it down completely.

Yes, I can reproduce this. VS

Steve_Lionel — Thu, 16 Aug 2018 22:43:34 GMT

Yes, I can reproduce this. VS complains that the Visual Fortran Expression Evaluator had an error. Please report this to Intel Support.

Steve,

David_DiLaura1 — Thu, 16 Aug 2018 23:37:29 GMT

Steve,

Your response suggests this is an Intel/Fortran problem . . . is that the case? The rest of our Team is using VS 15.7.5 with both Release 18.3 and 19.1 of the Fortran compiler without a problem. Will Intel have to change the compiler to be compatible with revision 15.8.0 of VS? Or do you think this is this a (new) bug in VS 15.8.0?

Intel folks: please weigh in on this issue.

I don't know whose bug it is,

Steve_Lionel — Fri, 17 Aug 2018 00:57:49 GMT

I don't know whose bug it is, but it is Intel's responsibility to get it fixed. They will work with Microsoft if need be. I note that more than one VS2017 update has broken the Intel Fortran VS integration, though not in this specific manner.

In this case it isn't the compiler, it's the "Fortran Expression Evaluator" which the debugger calls to show values of Fortran variables. Obviously something changed incompatibly, but whether it was an Intel bug or a Microsoft incompatible change, Intel is going to have to adjust.

Steve, Colleagues,

David_DiLaura1 — Fri, 17 Aug 2018 16:09:47 GMT

Steve, Colleagues,

Does anyone know how (if it's possible) to take VS back one release/upgrade? The alternative to uninstall and reinstall VS, compilers, tools, etc. on the workstation is a half-day loss.

Yes. This has ruined my life

Rob1 — Fri, 17 Aug 2018 17:05:13 GMT

Yes. This has ruined my life for the last 24 hours.

I am not aware of any way to

Steve_Lionel — Fri, 17 Aug 2018 18:52:49 GMT

I am not aware of any way to roll back a VS update.

As far as I know, Microsoft provides no advance notice/testing of VS updates to its integration partners. In this aspect they are as bad as Apple, and very different from the Windows team.

So who has filed a ticket with Intel on this?

Steve, Colleagues,

David_DiLaura1 — Fri, 17 Aug 2018 18:59:14 GMT

Steve, Colleagues,

Our team filed a ticket on this problem with Visual Studio late yesterday. The update from 2 hours ago is that they duplicated to problem and are "looking into it" Naturally, there's no way to know what that means. We'll go ahead a file a ticket with Intel as well.

Can you reproduce this with

Steve_Lionel — Sat, 18 Aug 2018 00:01:17 GMT

Can you reproduce this with an MSVC program?

VS 15.8.1 is out, doesn't

Steve_Lionel — Sun, 19 Aug 2018 23:44:42 GMT

VS 15.8.1 is out, doesn't resolve the problem.

Intel Support informed us

David_DiLaura1 — Mon, 20 Aug 2018 18:59:25 GMT

Intel Support informed us this morning that the ticket for this problem has been escalated to the IDE team.

I also posted this problem

NotThatItMatters — Sat, 25 Aug 2018 04:00:02 GMT

I also posted this problem with the VS team, but they needed a core dump to investigate. With VS spontaneously crashing, all I would get was a Windows Error Report (wer). If any of you know how to retrieve a memory dump accompanying a Windows Error Report, please post it here so I can forward it.

https://blogs.msdn.microsoft

Steve_Lionel — Sat, 25 Aug 2018 14:23:17 GMT

https://blogs.msdn.microsoft.com/chaun/2013/11/12/steps-to-catch-a-simple-crash-dump-of-a-crashing-process/ seems to be the method.

It appears 15.8.2 has not

NotThatItMatters — Wed, 29 Aug 2018 16:16:45 GMT

It appears 15.8.2 has not resolved the issue.

Compiler Release Notes were

Devorah_H_Intel — Wed, 29 Aug 2018 21:00:00 GMT

Compiler Release Notes were updated to include the following note:

Latest supported by Intel® Fortran Compiler 18.0 Update 3 version of Microsoft Visual Studio 2017* is 15.6.

https://software.intel.com/en-us/articles/intel-visual-fortran-compiler-180-for-windows-release-notes-for-intel-parallel-studio-xe-2018#sysreq

That being said, our engineering team is working on resolving all reported Microsoft VS integration issues related to Microsoft VS version 15.7 or later. These issues will be fixed in the upcoming compiler releases.

Good to hear this is being

j0e — Thu, 30 Aug 2018 15:13:05 GMT

Good to hear this is being addressed. Thanks!

There was an article by Steve

WSinc — Thu, 30 Aug 2018 23:07:59 GMT

There was an article by Steve about adding Fortran file extensions (.f90, etc)

but I could not get the same options in my version of VS 2017.

Under "Tools/options," the choice "Intel compilers" never comes up.

I have 15.7.5, but could not delete and reinstall an earlier version that works.

Dont they test this stuff before we have to deal with it ?

Yes, it is all tested. But

Steve_Lionel — Thu, 30 Aug 2018 23:51:14 GMT

Yes, it is all tested. But when Microsoft makes breaking changes after the release, there is little Intel can do about it.

Any updates on this topic? I

Chaudhary__Krishna — Fri, 07 Sep 2018 17:03:20 GMT

Any updates on this topic? I am having the same issue with the latest version of VS 15.8.3 as well. Any suggested workaround?

See #15. Your choices: i)

mecej4 — Sat, 08 Sep 2018 06:42:00 GMT

See #15. Your choices: i) install VS2017 15.6 or earlier, if you can find an installer, ii) install VS2015, iii) wait for Intel to release Parallel Studio/Composer 2019.

CORRECTION, added 13 September 2018:

The VS2017 15.6 sub-version currently available at https://docs.microsoft.com/en-us/visualstudio/productinfo/installing-an-earlier-release-of-vs2017 is 15.6.7. I found out that this version also has incompatibilities with Parallel Studio 2018, see the second paragraph of #25.

DEVORAH H., if you read this, please edit/update your post (#15) and the release notes by specifying the third part of the version number - i.e., the 'x' in 15.6.x. Otherwise, you may end up with a few upset customers.