Displaying 3 results from an estimated 3 matches for "linkerarg".
2016 Jan 22
3
lld: ELF/COFF main() interface
...on that you can call and that works as
expected.
Even if we want to call exec for whatever reason, we can copy in-memory
objects to shared memory objects and exec the linker, so the basic design
should work in such case too.
The function signature would be something like:
bool link(ArrayRef<LinkerArg> CommandLineArgs, MemoryBuffer &OutputFile,
std::string &ErrorMsg);
where the return value indicates success/failure. LinkerArg is a union type
of StringRef and MemoryBufferRef. The result is returned as OutputFile
memory buffer. If it prints out any message, ErrorMsg will hold it.
(I...
2016 Jan 22
2
lld: ELF/COFF main() interface
...en if we want to call exec for whatever reason, we can copy in-memory
>> objects to shared memory objects and exec the linker, so the basic design
>> should work in such case too.
>>
>> The function signature would be something like:
>>
>> bool link(ArrayRef<LinkerArg> CommandLineArgs, MemoryBuffer
>> &OutputFile, std::string &ErrorMsg);
>>
>> where the return value indicates success/failure. LinkerArg is a union
>> type of StringRef and MemoryBufferRef. The result is returned as OutputFile
>> memory buffer. If it prints...
2016 Jan 22
7
lld: ELF/COFF main() interface
> Also, one of the other possible motivations of using LLD directly from
Clang would be to avoid process overhead on operating systems where that is
a much more significant part of the compile time cost. We could today
actually take the fork out of the Clang driver because the Clang frontend
*is* designed in this way. But we would also need LLD to work in this way.
Then go change clang and