Displaying 3 results from an estimated 3 matches for "mdllvmmodule".
2015 Mar 20
2
[LLVMdev] New kind of metadata to capture LLVM IR linking structure
...ries) and have found it useful to be able to determine which
library a particular Instruction* or GlobalVariable* came from (e.g. so
that we can ignore some of them, or focus analysis on particular ones).
To preserve this information across linking, I've implemented a new kind of
metadata node MDLLVMModule that records:
1) Which LLVM modules (i.e. LLVM IR file) have been linked into this LLVM
module
2) Which compilation units directly contribute to this LLVM module (i.e.
that are not part of an LLVM submodule)
The format of the metadata looks like this:
!llvm.module = !{!0}
!0 = !MDLLVMModule(nam...
2015 Mar 23
4
[LLVMdev] New kind of metadata to capture LLVM IR linking structure
...on, Mar 23, 2015 at 9:50 AM David Blaikie <dblaikie at gmail.com> wrote:
> On Mon, Mar 23, 2015 at 8:15 AM, Khilan Gudka <Khilan.Gudka at cl.cam.ac.uk>
> wrote:
>
>> Hi David
>>
>> Thanks for your email.
>>
>> What's the benefit/purpose of the MDLLVMModule over just having the
>>> MDCompileUnits themselves? I would imagine the user cares about which
>>> source file the problem was in (obtained from the MDCompileUnit), not the
>>> sequence of BC modules that may've been built into?
>>>
>>
>> We envis...
2015 Mar 23
2
[LLVMdev] New kind of metadata to capture LLVM IR linking structure
Hi David
Thanks for your email.
What's the benefit/purpose of the MDLLVMModule over just having the
> MDCompileUnits themselves? I would imagine the user cares about which
> source file the problem was in (obtained from the MDCompileUnit), not the
> sequence of BC modules that may've been built into?
>
We envisage it to be useful when an analysis tool built u...