Displaying 2 results from an estimated 2 matches for "allowunresolvedsymbol".
Did you mean:
allowunresolvedsymbols
2015 Jun 30
2
[LLVMdev] ORC and relocations
...Rozenfeld
Cc: llvmdev at cs.uiuc.edu
Subject: Re: ORC and relocations
Hi Eugene,
Returning null addresses to the linker is unusual enough that I'd prefer to keep it as an error.
Could you return a non-zero marker value, e.g. all-ones? If not, we should add an option to RuntimeDyld like "AllowUnresolvedSymbols" and change the error condition to if '(!Addr && !AllowUnresolvedSymbols)'.
Cheers,
Lang.
On Thu, Jun 25, 2015 at 6:35 PM, Eugene Rozenfeld <Eugene.Rozenfeld at microsoft.com<mailto:Eugene.Rozenfeld at microsoft.com>> wrote:
Hi Lang,
Can you please let me know...
2015 Jun 26
2
[LLVMdev] ORC and relocations
Hi Lang,
Can you please let me know you think it would be right to modify RuntimeDyldImpl::resolveExternalSymbols to allow resolvers to return 0 addresses? Something like this would be ideal for me:
void RuntimeDyldImpl::resolveExternalSymbols() {
while (!ExternalSymbolRelocations.empty()) {
StringMap<RelocationList>::iterator i = ExternalSymbolRelocations.begin();
StringRef