Magnus,
Please formally report any cases where a current version compiler fails with any kind of traceback or unhandled exception.
The assertion message is a clue to the compiler engineers to help them find and fix the bug. It's not much use to the end user.
>updating the compiler is not an option in this particular case.
I don't understand why a fixed compiler is not an option. You've found a bug. The only way it will ever be fixed is by using a new version, (it may even have already been fixed). So, if you want the bug fixed, your only option is a new version.
Typically installing a new compiler is quick, simple and very low risk. As a rule compilers only ever get better. Regressions are very rare, as the qualification suite for compilers usually includes every failing program that has ever been elevated, so problems tend to stay fixed! (indeed, I remember one compiler engineer commenting that their verification & qualification suite was probably more valuable than their source code!)
Compilers are strictly user mode code. They're basically just text processors. It's always possible for an unprivileged user to take a later version of a compiler, place it in a private directory and use it without having to install it system wide. Some compiler installation kits give the option to save all old versions and select one on a process, group or system wide basis.
I recommend you unpack the latest compiler and test your code against it. If it still fails, submit your code to engineering. If not, you have evidence that upgrading to the latest compiler is worthwhile.
If none of that is acceptable, I guess you'll just have to put up with compiling with lower levels of optimisation.
A crucible of informative mistakes
