search for: _7success

...e default for Windows targets. Regarding merging of multiple modules: "But of course this would not work because as soon as I try to load the second script, I get a duplicate symbol error from LLVM (and this completely makes sense): [ERROR]: LLVM error: Duplicate definition of symbol '??_7success at lest@@6B@'" I think that anything that llvm-link can merge should, in theory, be safe to add to the JIT. This actually sounds like a bug. Are you able to share the full modules that you were merging? Regards, Lang. On Mon, Apr 27, 2020 at 11:11 AM David Blaikie <dblaikie at gmail...

...multiple modules: >> >> "But of course this would not work because as soon as I try to load the >> second script, I get a duplicate symbol error from LLVM (and this >> completely makes sense): >> >> [ERROR]: LLVM error: Duplicate definition of symbol '??_7success at lest >> @@6B@'" >> >> I think that anything that llvm-link can merge should, in theory, be safe >> to add to the JIT. This actually sounds like a bug. Are you able to share >> the full modules that you were merging? >> >> Regards, >> Lang....

Hello LLVM developers! So, I'm continuing my journey with my toy C++ JIT compiler implementation, and I wrote another article on the issues/solutions I've been working on in the past few days, mainly: - Precompiled header handling, - Emulated TLS desactivation, - Globals construction & destruction, - C++ exceptions handling, - Multi modules linking, => In case this could be

...> "But of course this would not work because as soon as I try to load the >>>> second script, I get a duplicate symbol error from LLVM (and this >>>> completely makes sense): >>>> >>>> [ERROR]: LLVM error: Duplicate definition of symbol '??_7success at lest >>>> @@6B@'" >>>> >>>> I think that anything that llvm-link can merge should, in theory, be >>>> safe to add to the JIT. This actually sounds like a bug. Are you able to >>>> share the full modules that you were merging? &...