I at all times look ahead to putting in a brand new replace of IFX within the hope that it’s going to enable me to start out utilizing it for my growth work and eventually depart IFORT behind. Though some headway has been made because the earlier replace from final 12 months, a fascinating consequence will not be but potential.

Firstly the set up, whereas faster than earlier than which is nice, however throws up some uncertainty with warning messages that do not make a lot sense to me.

Simply Put in the newest replace on each Home windows 10 & 11 and I’ve a number of points to report. I’ve put in the OneAPIBase & OneAPIToolkit which appeared to work with no drawback.

Nevertheless once I open VS (see attachment for VS settings)  I get a warning message.

which directs me to the next file:

C:UsersSteveAppDataRoamingMicrosoftVisualStudio17.0_53ecf6c1ActivityLog.xml (hooked up) which incorporates reviews of a number of errors.

Is it secure to disregard these warnings? What’s the trigger?

On the laptop computer (Home windows 11) the dialog bins, the place you choose the x64 IFX / IFORT x64 compilers (Instruments-Choices-Compilers Menu), are usually not correctly displayed as proven under.

These dialog bins don’t have any means to resize so their contents stay undecipherable.

They do nevertheless look OK on my desktop which remains to be working beneath Home windows 10.

If that is brought on by VS model, is there a approach to cease it updating because it appears to take action with out me having any probability to cease it?

After I restart VS, as instructed, that message remains to be getting displayed and the show remains to be the identical

Points relating particularly to IFX vs IFORT are:

I’ve nonetheless to efficiently compile and hyperlink my full challenge options with out compromises (which incorporates 36 initiatives) in IFX so must carry on utilizing IFORT till these get resolved. I’m solely utilizing the x64 compilers.

1) The Launch construct will not compile a number of information until the Optimisation (/Od) is totally disabled in some (although not all the information). Not one of the different optimisation choices work. I’ve beforehand reported these ICEs (with instance reproducer) after making an attempt earlier subject again in December to Premier Assist, so sadly it seems that this subject has nonetheless to be correctly resolved. I did use the instructed workaround (to disable the optimisation) so some progress of types. The change on this setting might nicely have a detrimental have an effect on the velocity of this system in comparison with IFORT. After altering to /Od this system does really hyperlink and run in Launch mode from inside VS.

As Intel must be already conscious of such points, it could be helpful to know if they’ve made any progress on a repair, or no less than recognized what’s inflicting the ICE. Perhaps my coding is in charge however I don’t see any apparent sample and I don’t use any multi-core stuff.

2) The Debug compilation construct is issuing messages saying that the /verify:uninit will not be at present out there on Home windows. Is there a substitute for this compiler possibility in IFX or will it’s made out there in a later launch or has it been deprecated?

3) Throughout the linking section of the Debug configuration I get seemingly random messages which quote odd particular person information inside libraries like:

deadly error LNK1220: ‘resolving static reference image’ requires ‘/WOWA64’ specification

Consequently the Debug configuration will not efficiently full.

Any suggestions from Intel can be a lot appreciated? You appear to be getting there eventually however nonetheless a bit to go.

The earlier I can efficiently migrate to IFX the higher as I will not must waste time and area having to keep up the IFORT model as a backup.

Thanks

Steve