Home Dashboard Directory Help

Visual Studio 2012 Express: /Qpar-report:2 works in Win32, fails to report in x64 projects by John Michael Reed


 as By Design Help for as By Design

Sign in
to vote
Type: Bug
ID: 785675
Opened: 4/26/2013 6:54:09 AM
Access Restriction: Public
User(s) can reproduce this bug


In Microsoft Visual Studio 2012 Express, programming in C++, the "/Qpar-report:2" command line option works in Win32, but fails to report on auto parallelization in x64 projects. I do not think that this should happen when I change the configuration manager project settings from 32 bit to 64 bit (unless Auto-Parallelization and Auto-Vectorization is only supposed to work on 32 bit applications or because this feature in x64 was only made available on VS Professional and up). Is this supposed to happen? For more details, see forum question:

Sign in to post a comment.
Posted by Microsoft on 5/7/2013 at 3:52 PM
Hi, I think you may just have some missing project settings.

The project file you attached has a Win32 configuration, but no X64 one. The win32 one is 'debug', but it looks like you have manually changed /O2, as well as /Qpar /Qpar-report:2. I don't see the associated x64 one, but I can compile the code as expected on the command line just fine.

Please double check that you have optimizations turned on, plus /Qpar /Qpar-report:2 set. You can always verify the switches actually getting thrown in ConsoleApplication1.log files.

If you are still seeing problems, can you please provide the precise solution that exhibits it?

I am closing this MSConnect item. Feel free to re-open it if you have any more questions.

Eric Brumer - Microsoft Visual C++
Posted by Microsoft on 4/28/2013 at 8:40 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Microsoft on 4/26/2013 at 7:52 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.