search for: assertf

...ng assert: assert(Op.getValueType() !=MVT::Other && Op.getValueType() != MVT::Flag && "Chain and flag operands should occur at end of operand list!"); In order to understand which operand was causing the failure, I need to dig quite a lot. What I propose is that an 'assertf' function be added, which wraps assert and sprintf. This would allow the 'missing' information to be added to assertion messages. This (imo) would be the BestThing ;) Thoughts?

Here's an example of how this would be used: In the constructor for ConstantVector, there's an assert: assert(C->getType() == T->getElementType() && "Initializer for vector element doesn't match vector element type!"); I would change this to: ASSERT_STRM(C->getType() == T->getElementType(), "Initializer for vector element "