Displaying 3 results from an estimated 3 matches for "libpolicy".
2015 Mar 23
2
[LLVMdev] New kind of metadata to capture LLVM IR linking structure
...rm this analysis we
have to link them all together into a single .bc/.ll file.
Having the module structure allows us to model interactions between
different modules (without manually (and sometimes unreliably) having to
work out which source file corresponds to which library (e.g. libssl,
libpci, libpolicy, librenderer, etc)). It also allows an analysis tool to
support turning on/off output warnings for particular libraries (as they
can lead to a lot of analysis output).
>
>
>>
>> I would be very grateful if someone could review this.
>>
>> Thanks
>>
>> --...
2015 Mar 23
4
[LLVMdev] New kind of metadata to capture LLVM IR linking structure
...ogether into a single .bc/.ll file.
>>
>> Having the module structure allows us to model interactions between
>> different modules (without manually (and sometimes unreliably) having to
>> work out which source file corresponds to which library (e.g. libssl,
>> libpci, libpolicy, librenderer, etc)). It also allows an analysis tool to
>> support turning on/off output warnings for particular libraries (as they
>> can lead to a lot of analysis output).
>>
>
> Fair enough - I've no idea/opinion on whether that's the right abstraction
> (other...
2015 Mar 20
2
[LLVMdev] New kind of metadata to capture LLVM IR linking structure
Hello all
llvm-link merges together the metadata from the IR files being linked
together. This means that when linking different libraries together (i.e.
multiple source files that have been compiled into a single LLVM IR file)
it can be hard or impossible to identify the library boundaries.
We're using LLVM to do static analysis of applications (together with their
dependent libraries) and