[PATCH] LTO: introduce object file-based on-disk module format.

[Eric Christopher]

Hi Peter,

If the imports are for .o files and the bitcode is for before compilation
is complete? If it's post compilation then we'll have a .o file and can put
the metadata in as normal? Otherwise if we're using lazy compilation you'll
need to teach something how to read llvm-ir anyhow and so might as well not
bother storing it in an elf file?

I could easily be missing something of the compilation pipeline here.

-eric

On Wed, May 13, 2015 at 2:59 PM Peter Collingbourne <peter at pcc.me.uk> wrote:

> Hi Eric,
>
> Have you seen my original proposal? (
> http://lists.cs.uiuc.edu/pipermail/llvmdev/2014-July/074540.html) In the
> second paragraph in particular it explains how llgo uses this feature.
>
> Peter
>
>
> REPOSITORY
>   rL LLVM
>
> http://reviews.llvm.org/D4371
>
> EMAIL PREFERENCES
>   http://reviews.llvm.org/settings/panel/emailpreferences/
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20150513/8a14738c/attachment.html>