Displaying 3 results from an estimated 3 matches for "8309df13".
2011 Jul 26
0
[LLVMdev] Proposal for better assertions in LLVM
> #define ASSERT_STRM(cond, args) \
> if (!(cond)) AssertionFailureStream(__FILE__, __LINE__) << args
>
> Note that there's no trailing semicolon, as this is supplied at the
> point where the macro is invoked.
>
> What do you think?
Neat, but inducing a debug trap is even more useful on asserts (optionally).
2011 Jul 26
2
[LLVMdev] Proposal for better assertions in LLVM
...on asserts
> (optionally).
>
What's the best way to do that? I'd like to incorporate it into my
frontend's diagnostics.
--
-- Talin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110726/8309df13/attachment.html>
2011 Jul 26
5
[LLVMdev] Proposal for better assertions in LLVM
The assertions in LLVM would be a lot more useful if they could print out
not only the source code of the expression that failed, but also print the
values of the various arguments. To that end, I have an idea for an improved
assert macro which would use raw_ostream. It would look something like this:
ASSERT_STRM(Ty == STy, "Expected " << Ty << " but got "