search for: r218078

...bitcode as bitcode. And the LTOModule::createFrom*/lto_module_create* routines correctly parse the native object-wrapped bitcode and return an LTOmodule. As a result, the llvm-lto tool that also uses libLTO interfaces didn't require any changes when the native-wrapped reading support went in (r218078), and is able to handle native-wrapped bitcode out of the box. > > Handling the function index/summary behind an API sounds like a good idea. I am going to work on fleshing out this part next so that the actual format of the files is hidden from clients. Thanks, Teresa > > On Fri, M...

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.