Internal compiler error - by trashproxy

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 770707 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 11/11/2012 1:02:06 AM
Access Restriction Public


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.

Sign in to post a comment.
Posted by Deon [MSFT] on 4/29/2014 at 12:31 PM
Thank you for reporting this issue. This issue has been fixed in Visual Studio 2013. You can install a trial version of Visual Studio 2013 with the fix from:
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 Macy [MSFT] 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 Helen [MSFT] 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 Helen [MSFT] 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 Helen [MSFT] 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 Macy [MSFT] 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(