Selectively changing compile options, large projects

[jarvusluntatintel]

I periodically will change the compile options for some of my subroutines by highlighting the files, right clicking and selecting properties. Even when I changed half the files in my project (trying to isolate problems), maybe ~1000 files, it only took a few seconds With vs 2005 and Intel 9. I just tried this with vs 2005 and Intel 11 and it took a half hour. Is this a known bug with the newer version, or the consequences of a new feature (I notice changed files have a red mark), or a problem on my computer?

My program currently requires Qsave and Qzero to run correctly. I'm trying to figure out why. When I selected half of the files and turn Qsave off, I immediately got the hour glass, wait cursor (I had not yet pressed ok/apply). Fifteen minutes later it came back ok. Turning Qzero off took another fifteen minutes. This is going to make it very painful to track down which subroutines actually require Qsave and Qzero (and need fixing) and which ones don't. (As an aside, I've tried static verify, but there is so much legacy code and so many warnings about code that, while sloppy, actually does work ok,that I gave up on it.) If nothing else, it would be nice if I could change both options before the fifteen minute wait.

[Steven_L_Intel1]

The little red mark is Visual Studio's way of telling you that the file has custom properties that override the project's.

I have not heard of this being an issue and will try it myself to see.

[jimdempseyatthecove]

Jarvus,

While waiting for fix from Intel, you could partition your 1000's of files into multiple projects (that build libraries). Then on your hunt for bug, toggle the properties on the project first (one by one). When you find the project sensitive to the optimization, then pick away at the files within the sub project. This should be 10x faster when you have 10 projects (assuming linear wait time).

Jim Dempsey

[Steven_L_Intel1 · Accepted solution]

I have reproduced the problem and reported it to the developers. The issue ID is DPD200117749.