I all the time 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 improvement work and eventually go away IFORT behind. Though some headway has been made because the earlier replace from final 12 months, a fascinating consequence just isn’t but attainable.

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 just a few points to report. I’ve put in the OneAPIBase & OneAPIToolkit which appeared to work with no downside.

Nonetheless after 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 accommodates 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), usually are 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 below Home windows 10.

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

After I restart VS, as recommended, 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 undertaking options with out compromises (which accommodates 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 except the Optimisation (/Od) is absolutely 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 attempting earlier problem again in December to Premier Assist, so sadly it seems that this problem has nonetheless to be correctly resolved. I did use the recommended workaround (to disable the optimisation) so some progress of kinds. The change on this setting might effectively have a detrimental have an effect on the pace 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 needs to be already conscious of such points, it might be helpful to know if they’ve made any progress on a repair, or at the very least recognized what’s inflicting the ICE. Perhaps my coding is responsible 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 just isn’t at present obtainable on Home windows. Is there a substitute for this compiler choice in IFX or will it’s made obtainable in a later launch or has it been deprecated?

3) Through the linking part 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 could 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 should waste time and area having to keep up the IFORT model as a backup.

Thanks

Steve