[LLVMdev] ARM MC .s status?
espindola at google.com
Tue Sep 14 18:58:40 CDT 2010
> Semi off the top of my head, I'd expect the normal code path for that to still go through the linker rather than being emitted directly. If nothing else, to resolve any symbols that need to be brought in from static libs. That said, in combination with the LTO and perhaps some additional restrictions (no static symbol dependencies, etc.), I don't see any reason why there couldn't be a .so emitter.
That is more or less the idea we were playing with. When producing a
.so for PNaCl, all files going into the library must be bitcode files,
but there can be external .so ELF dependencies. Using gold we should
be able to record the dependencies somewhere and output a combined
A custom translator can then be written that takes the combined
bitcode and the dependencies and produces a .so in one step. Ideally
the dependencies would be encoded in the .bc itself, so we would have
a single file going in for each .so.
Rafael Ávila de Espíndola
More information about the LLVMdev