Internal compiler error | Microsoft Connect

Internal compiler error by trashproxy

Closed

as Fixed

Type:	Bug
ID:	770707
Opened:	11/11/2012 1:02:06 AM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

I compiled a program (on the command line using nmake and cl) with Intel's AVX2 intrinsic '_mm256_srli_epi64(sum1, 128)' and got an internal compiler error.

Changing '128' to '127' or less (down to 0) does not generate the error.

Details (expand)

Visual Studio 2012

Write a program using Intel's AVX2 intrinsic '_mm256_srli_epi64(sum1, 128)' and compile it.

English

Windows 7

English

source_file.cpp
<path_to_my_source_file.cpp> : fatal error C1001: An internal error has occurred in the compiler.
(compiler file 'f:\dd\vctools\compiler\utc\src\p2\main.c', line 211)
To work around this problem, try simplifying or changing the program near the locations listed above.
Please choose the Technical Support command on the Visual C++
Help menu, or open the Technical Support help file for more information
INTERNAL COMPILER ERROR in 'C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\BIN\cl.EXE'
Please choose the Technical Support command on the Visual C++
Help menu, or open the Technical Support help file for more information
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\BIN\cl.EXE"' : return code '0x1'
Stop.

Warning about trying to shift 128 bits (when 127 seems to be the maximum allowed number of bits to shift, although 64 or less probably is more adequate)

0 attachments

Posted by trashproxy on 11/19/2012 at 11:47 AM

1. Write a program using Intel's AVX2 intrinsic '_mm256_srli_epi64(sum1, 128)' and you will get an internal compiler error instead of a warning.

Here is an example of such a program called 'gcc4ever.cpp':

#include <immintrin.h>
int main()
{
__m256i foo = _mm256_srli_epi64(foo, 128);
return 0;
}

2. Compile with on the "Developer Command Prompt":

cl gcc4ever.cpp

3. Enjoy the internal compiler error.

Posted by Microsoft on 11/19/2012 at 3:03 AM

Hello again. We wanted to give you a quick reminder that to efficiently investigate and reproduce your issue, we need you to submit the additional information we requested. If we haven't heard back from you with the requested information in the next 3 days, we will go ahead and close the issue.

Posted by Microsoft on 11/15/2012 at 12:10 AM

Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Posted by Microsoft on 11/15/2012 at 12:09 AM

I am currently standing by for an update from you and would like to know how things are going on your end. If you could get back to me at your earliest convenience with information I request, we will be able to make headway towards a resolution. I look forward to hearing from you.

Posted by Microsoft on 11/11/2012 at 10:35 PM

Thank you for submitting feedback on Visual Studio and .NET Framework. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please give us a demo project to demonstrate this issue so that we can conduct further research?

We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team

Posted by Microsoft on 11/11/2012 at 1:51 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)