b20c4fc8ef
After the most recent changes, I noticed that the matrix unit test started failing for some optimized compiles. I'm not sure if it was these changes or others. What I think happened is that it was a check for a Matrix operation that should be invalid. It checked the valid flag without checking the data (which, of course, is invalid). However, I think the optimizer saw that the data generated was never used so removed that part of the computation so the invalid flag was never set. Add a condition that uses the result even though it should never be called to hopefully force the compiler to compute it. |
||
---|---|---|
.. | ||
CMakeLists.txt | ||
OptionParser.h | ||
Testing.h | ||
TestingImplicitFunctions.h | ||
TestingMath.h | ||
UnitTestBinaryOperators.cxx | ||
UnitTestBinaryPredicates.cxx | ||
UnitTestCellShape.cxx | ||
UnitTestImplicitFunctions.cxx | ||
UnitTestListTag.cxx | ||
UnitTestMath.cxx | ||
UnitTestMatrix.cxx | ||
UnitTestNewtonsMethod.cxx | ||
UnitTestPair.cxx | ||
UnitTestTesting.cxx | ||
UnitTestTypeListTag.cxx | ||
UnitTestTypes.cxx | ||
UnitTestTypeTraits.cxx | ||
UnitTestUnaryPredicates.cxx | ||
UnitTestVecRectilinearPointCoordinates.cxx | ||
UnitTestVectorAnalysis.cxx | ||
UnitTestVecTraits.cxx | ||
UnitTestVecVariable.cxx | ||
VecTraitsTests.h |