[LLVMdev] Building a stable bitcode format for PNaCl - based on LLVM IR

[Eli Bendersky]

On Fri, Aug 9, 2013 at 9:12 AM, Rafael Espíndola <rafael.espindola at gmail.com
> wrote:

> > The document is available as a PDF here:
> >
> https://docs.google.com/a/chromium.org/viewer?a=v&pid=sites&srcid=Y2hyb21pdW0ub3JnfGRldnxneDo0OWYwZjVkYWFjOWNjODE1
> >
> > And in text here:
> >
> https://sites.google.com/a/chromium.org/dev/nativeclient/pnacl/stability-of-the-pnacl-bitcode-abi
>
> First, sorry for jumping in an old thread. I had this marked but had
> not been able to read it before.
>
> The document talks about ABI stability, but it is a bit unclear how
> far this goes. From older discussions, there are/were 3 interesting
> cases
>
> 1 Loading a stand alone application (pexe) in a new VM/browser.
> 2 Using a native library compiled with SDK N in an IR application
> compiled with  SDK M.
> 3 Using a IR library compiled with SDK N in an IR application compiled
> with SDK M.
>
> The document discusses 1. Items 2 and 3 are probably harder, but not
> mentioned. Is there any support for user provided dynamic libraries?
>

Hi Rafael,

In the first release, there is no support for user-provided dynamic
libraries. The user is expected to compile her whole application statically
into a single .pexe and distribute that. We do plan to add "dynamic"
libraries in future releases, and we tried to construct the ABI spec in a
way that would not interfere with these plans.

Eli
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130809/13a823da/attachment.html>