Displaying 3 results from an estimated 3 matches for "aspart".
Did you mean:
apart
2016 Jan 26
2
lld: ELF/COFF main() interface
The context issue may be solved by making all functions and context data
members of a class. Sort of having the convenience of global variables
accessible from all linker functions but without the regular global
variable problems of initializing and re-entry. so the class is suitable
aspart of a library. Most clang and LLVM classes works this way, not
passing contexts around.
2016-01-22 6:25 GMT+02:00 Rui Ueyama via llvm-dev <llvm-dev at lists.llvm.org>:
> There is a trade-off. In order to use main as a library function, all
> functions behind it have to pass around a c...
2016 Jan 26
6
lld: ELF/COFF main() interface
...and context
> > data
> > members of a class. Sort of having the convenience of global
> > variables
> > accessible from all linker functions but without the regular global
> > variable
> > problems of initializing and re-entry. so the class is suitable
> > aspart of a
> > library. Most clang and LLVM classes works this way, not passing
> > contexts
> > around.
>
> That is a way to solve the global variable problem. The bigger
> problem
> is the error handling. We can use a diagnostic handler instead of
> calling exit, but w...
2016 Jan 22
2
lld: ELF/COFF main() interface
> If I were a user, I definitely want the former instead of the latter
because the former just provides more.
This is if you wanted to use the library (e.g. embed linker into clang, do
parallel linking of many executables from the same process, etc.). For some
use cases there's no difference because the only thing you'll do with a
library is link it into a command-line executable and