Inconsistency with description of /QxHost command line option

[SergeyKostrov]

I detected a small issue related to /QxHost command line option for Intel C++ compiler on Windows platforms. In command line help a description is:

/QxHost   generate instructions for the highest instruction set and processor available on the compilation host machine

and

in a Visual Studio IDE:

The processor performing the compilation

Please take a look at enclosed screenshot ( NoteL It looks like a developer could "send" some C/C++ sources to a CPU and they will be "compiled" by the CPU ):

<img src="software.intel.com/sites/default/files/forum/373678/qxhostoption.jpg"/>

[SergeyKostrov]

By some reason it wasn't displayed...

[TimP]

Yes, if you set /QxHost in your project, the instruction set will be chosen according to the CPU on which the compilation takes place.

If your point is that the descriptions of the choices aren't particularly useful without looking up background material, I couldn't agree more.

[SergeyKostrov]

I simply wanted to bring attebtion that: >>In command line help a description is: >> >>/QxHost generate instructions for the highest instruction set and processor available on the compilation host machine I consider as Correct >>and >> >>in a Visual Studio IDE: >> >>The processor performing the compilation I consider as Incorrect ( very confusing ) and it needs to be updated to match to the description of the command line help. Note: I'm talking about descriptions of the /QxHost option. I'm Not talking about what the option actually does.

[Alexander_W_Intel]

Hi Sergey,

thanks for bringing this issue to our attention. I also think the description in Visual Studio could be more clear. I will forward your suggestion to our documentation team. 

Thanks,
Alex  

[Alexander_W_Intel · Accepted solution]

Hi Sergey,

the wording is changed in the actual releases to: "Same as the host processor performing the compilation (/QxHost)" in the Visual Studio IDE.

Thanks,
Alex 

[SergeyKostrov]

Hi Alex, Thanks and sorry for a delay with my response.