The problem is that you are doing an endless loop and I think the error message you see was due to running out of memory.
I was able to run the task by modify your code to
or if you want to keep the endless loop just print out some of the result so the program wont run too fast and hit the memory limit
thanks for your answer. But I don't think this is the problem.
1. The program runs just fine, if I run only one thread.
2. The program also crashes in most cases, if I do not keep the endless loop. In fact, sometimes it crashes in the first loop (debugger says i=0).
I think it has something to do with the internal memory management of ACML. Right now I use another blas library and my program works without any problems.
I am currently facing the same problem with the latest 6.0.6 version.
I was using Visual Studio 2013, and I downloaded acml-184.108.40.206-ifort64.zip. I used single threaded version of the library.
I ran the original poster's program,with finite number of loop. This is what I got:
First-chance exception at 0x0000000076DFE4E4 (ntdll.dll) in test.exe: 0xC0000005: Access violation writing location 0x0000000000000024.
Unhandled exception at 0x0000000076DFE4E4 (ntdll.dll) in test.exe: 0xC0000005: Access violation writing location 0x0000000000000024.
Did I do something wrong?