11 Apr
2010
11 Apr
'10
3 p.m.
The assertion only occurs in Boost 1.40 not in 1.36. Is this known behavior? Kind regards, Moritz Ion Gaztañaga wrote:
On 09/04/2010 18:19, Moritz wrote:
Because of this I now think that gcc messes up the optimized code or I made a major programming mistake.
A similar bug has been reported to Boost.Trac and I think it's related to a gcc optimization bug.
Best,
Ion