5a3d51e3e7
Forgot to test at DEBUG=0. Both of these are basically cases where the new DEBUG_ASSERT_COND should be used, since the default DEBUG_ASSERT will now always emit code that gets cleaned up in the optimizer.
From 'Stellarisware from TI' version 9453