Displaying 3 results from an estimated 3 matches for "7d590ced".
2013 Dec 17
0
[LLVMdev] Debug Info Verifier: should we create a module pass for it?
My off the cuff idea here is to make it a module pass, but we'll split the
verification a bit:
a) IR verification time -
Verify debug metadata attached to instructions (i.e. line information).
Only check it for structure (i.e. do the various metadata nodes have the
right number and kind of operands).
b) Module pass -
Walk down from the CUs in the file and verify everything we see. I think
2013 Dec 19
1
[LLVMdev] Debug Info Verifier: should we create a module pass for it?
...verifier, each will traverse the module.
>>
>> Comments and suggestions are welcome.
>>
>> Thanks,
>> Manman
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131218/7d590ced/attachment.html>
2013 Nov 19
2
[LLVMdev] Debug Info Verifier: should we create a module pass for it?
Hi all,
Currently, debug info verifier is part of the IR verifier which is a
function pass.
One part of the IR verifier that I don't like is it verifies module-level
data in doFinalization. If we have two verifier passes in a single module
pass manager, doFinalization of the two passes will run on the same module
data after all passes.
I followed the same model for debug info verifier: