llvm dev - Nov 2015 - dump intermediate state of a module or a function

I want to dump an unfinished state of the whole IR of a module or
function for debugging purposes.

`llvm::WriteBitcodeToFile` does not suit my needs since it calls
validations on the module that will be failed in general for an
unfinished IR

Even debugging with lldb, sometimes is very hard to detect why the
same code generation works correctly in some cases, and in others the
llvm will trigger an invalid cast assertion. Having a partial state of
the IR for debugging would really, really help me out to reject
possible issues

Can you use module->dump()?

Regards,

Xiangyang

2015-11-03 19:14 GMT-05:00 charles quarra via llvm-dev <
llvm-dev at lists.llvm.org>:
> I want to dump an unfinished state of the whole IR of a module or
> function for debugging purposes.
>
> `llvm::WriteBitcodeToFile` does not suit my needs since it calls
> validations on the module that will be failed in general for an
> unfinished IR
>
> Even debugging with lldb, sometimes is very hard to detect why the
> same code generation works correctly in some cases, and in others the
> llvm will trigger an invalid cast assertion. Having a partial state of
> the IR for debugging would really, really help me out to reject
> possible issues
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20151103/92607ed1/attachment.html>