Displaying 3 results from an estimated 3 matches for "emacscriten".
2011 Dec 14
0
[LLVMdev] [RFC]Extending lib/Linker to support bitcode "shared objects"
...chieved with gold + gold plugin (with mods to both parts), but I
> would like to stay away from this dependency. Partly, because
> maintaining modified gold and gold plugin is no fun, partly because gold
> + gold plugin is hardly broken under cygwin.
I understand. I was just pointing that emacscriten case looks different
from what you have. I don't see where an LLVM IL library (libc in your
example) would fit. All that is needed is a stub with the functions that
will be defined in JS in the end.
Cheers,
Rafael
2011 Dec 12
2
[LLVMdev] [RFC]Extending lib/Linker to support bitcode "shared objects"
On Sun, Dec 11, 2011 at 2:19 PM, Rafael Ávila de Espíndola <
rafael.espindola at gmail.com> wrote:
> On 08/12/11 03:56 PM, Ivan Krasin wrote:
> > Hi llvm team!
> >
> > I'm currently working on the extended version of llvm-ld, which has an
> > ability to check if all the symbols present (and fail if some symbols
> > are not resolved), treat archives in
2011 Dec 14
2
[LLVMdev] [RFC]Extending lib/Linker to support bitcode "shared objects"
...plugin (with mods to both parts), but I
> > would like to stay away from this dependency. Partly, because
> > maintaining modified gold and gold plugin is no fun, partly because gold
> > + gold plugin is hardly broken under cygwin.
>
> I understand. I was just pointing that emacscriten case looks different
> from what you have. I don't see where an LLVM IL library (libc in your
> example) would fit. All that is needed is a stub with the functions that
> will be defined in JS in the end.
>
bitcode "so" is supposed to have the form of:
define void @printf...