27 Nov
2007
27 Nov
'07
3:41 p.m.
On 26/11/2007, Bryan Green
I'm forced to take boost::array out of my computation's inner loop. Is this a previously known issue? Any ideas why this performance discrepancy might exist?
I know that boost::array asserts that the index is in-range when using operator[] (as it's caught a few bugs for me), but that's an overhead that -O3 isn't going to eliminate. As KSpam mentioned, try with -DNDEBUG as well. ~ Scott -- Sed quis custodiet ipsos custodes?