search for: emutls_v

...n the process of porting our ORC code to ORC v2 and LLJIT. Now that I have worked around a problem getting global constructors to be called, everything seems to work unless a module declares a static thread-local variable. In that case I get a "JIT session error" saying that the symbol __ emutls_v.xyz was not found (substitute the mangled variable name for "xyz"). Does that mean anything to anybody out there? (I don't know if it's relevant, but we are using LLVM 8, and we are using Clang to compile C++ modules that are all put into a single JITDylib.) Geoff -------------...

...e to ORC v2 and LLJIT. Now that >> I have worked around a problem getting global constructors to be called, >> everything seems to work unless a module declares a static thread-local >> variable. In that case I get a "JIT session error" saying that the symbol __ >> emutls_v.xyz was not found (substitute the mangled variable name for >> "xyz"). >> >> Does that mean anything to anybody out there? >> >> (I don't know if it's relevant, but we are using LLVM 8, and we are using >> Clang to compile C++ modules that are a...

...e to ORC v2 and LLJIT. Now that >> I have worked around a problem getting global constructors to be called, >> everything seems to work unless a module declares a static thread-local >> variable. In that case I get a "JIT session error" saying that the symbol __ >> emutls_v.xyz was not found (substitute the mangled variable name for >> "xyz"). >> >> Does that mean anything to anybody out there? >> >> (I don't know if it's relevant, but we are using LLVM 8, and we are using >> Clang to compile C++ modules that are a...