From: Roland Schwarz (roland.schwarz_at_[hidden])
Date: 2006-12-15 09:01:46
Anthony Williams wrote:
> That's good as a workaround. It loses some of the error message benefits, but
> it's better than a compiler fault.
I tried to carefully follow the suggestions on the compiler help page
for ICE's in P2:
Turn off all optimizations (/O...) until the error goes away, then turn
each one on. So I arrived at:
This gives a clean compile. So it should be sufficient for this compiler
to run the tests with this option.
The page further suggest to find the function where the fault actually
is triggered and disable the optimization by guarding with pragmas.
I don't know if it is worth the effort. Since the compiler can be
expected to be retired after RC_1_34_0 release. Yes?
But what, if the error is not related to the test library? Would users
compiling <variant>release be affected too?
Another thing I noticed: The test library is built with
<asynch-exceptions>on while every other is with synch exceptions (/EHs).
I do not know about this issue to tell if it is a problem.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk