I just downloaded thetrial version of Intel Compiler. Iinstalled it inVisual Studio .NET 7.0 without a glitch.
I am developing one mid-sized program (about 1.7MB of C++source code), and I wondered if switching to Intel compiler would produce the prefromance benefits.
First time around, I compiled my program without a problem (optimizedcompilation was much slower than VS .NET - it does not matter much anyhow, run time is allwhat matters with optimizing compilers).
Then I set parameters: "/GL, equiv. to /Qipo" and started installation. Initial compilation of files went fine, individual IPOs went fine too, but when the accross the files (whole program) optimization started - compiler started earting computer'smemory and finaly hit 2GB of allocated memory and was shot down by Windows. Nointerim messages where output during this time.
It allworks againif I disable this optimization - but the whole idea is to extract the maximum optimized performance... so I need "/GL, equiv. to /Qipo" so that switching to Intel makes sense.
Also... I have one another problem, but I leave fixing it when and if I fix this major one.
What is the problem? How can I fix this? Any advices?