[llvm-dev] C++ JIT Compiler with LLVM on Windows 10 - part 5
Emmanuel Roche via llvm-dev
llvm-dev at lists.llvm.org
Thu Apr 1 01:09:53 PDT 2021
Hi Geoff!
It's nice to see that other people are following this "adventurous path"
;-) But unfortunately, I'm afraid, I don't have anything new to submit on
this topic: I basically stopped working on those LLVM tests shortly after
that last discussion, since I shifted my focus to different
tasks/concerns... :-( Eventually I would like to get back to it, but
realistically this is not going to happen anytime soon.Now, last thing I
see from the notes I took (but you probably already noticed that) was that
I seemed to have reached a point where my tests were working as expected
despite this limitation, using the code I took from llvm-link (as described
in that section
https://wiki.nervtech.org/doku.php?id=blog:2020:0425_jit_compiler_part5_improvements#jit_modules_linking_process
): so I'd say that was a working workaround in my case... but not sure it
could apply in your situation depending on your whole
"sources/bytecode/module processing path"...
=> But anyway, I wish you good luck if you decide to get your hands dirty
on that!
Cheers,
Manu.
Le mer. 31 mars 2021 à 15:09, Geoff Levner <glevner at gmail.com> a écrit :
> Hi Emmanuel and Lang,
>
> I am tuning in to this thread several months late, because I am just now
> trying to port our ORC-based application to Windows, and I am running into
> all the same problems that Emmanuel ran into. To avoid unresolved symbols I
> have had to compile JIT modules with -D_DLL; I have had to export
> RTTI-related symbols explicitly with the same trick that Emmanuel found;
> and now I have multiple definitions of ??_7exception at std@@6B@, like
> Emmanuel.
>
> I see this bug has not been fixed, so my question is mostly for Emmanuel:
> have you found a workaround? I don't know exactly when this symbol is
> generated, but I have C++ modules that cannot be JIT compiled as a result...
>
> Geoff
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20210401/1a7bbffd/attachment.html>
More information about the llvm-dev
mailing list