Displaying 2 results from an estimated 2 matches for "lto_module_".
Did you mean:
lto_module_t
2015 Jun 03
4
[LLVMdev] Updated RFC: ThinLTO Implementation Plan
...t
> straight forward as we cannot distinguish them just by looking at the
> file header alone, we would need to parse the sections and look for a
> .llvmbc section. We then need to add special handling of these native
> object wrappers.
Ok, I see. Does it help that there are LTOModule (lto_module_* in the
C API) interfaces for checking if a file contains bitcode (regardless
of whether it is straight-up or native-wrapped)? I don't know how hard
in your linker it is to query these when deciding whether to treat the
object file as bitcode or not, or how hard it is to pass the resulting
obje...
2015 May 29
4
[LLVMdev] Updated RFC: ThinLTO Implementation Plan
On Fri, May 29, 2015 at 6:56 AM, Alex Rosenberg <alexr at leftfield.org> wrote:
> My earlier statement about wrapping things in a native object file held in that it is controversial. It appears to be still central to your design.
>
> It may help to look at the problem from a different viewpoint: LLVM is not a compiler. It is a framework that can be used to make compiler-like tools.