[llvm-dev] C++ JIT Compiler with LLVM on Windows 10 (original) (raw)
Geoff Levner via llvm-dev llvm-dev at lists.llvm.org
Wed Mar 31 06:14:37 PDT 2021
- Previous message: [llvm-dev] C++ JIT Compiler with LLVM on Windows 10 - part 5
- Next message: [llvm-dev] Support of Big archive (AIX archive)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Here, by the way, is the original thread, which I could not figure out how to quote in my message: https://lists.llvm.org/pipermail/llvm-dev/2020-May/141444.html
On Wed, Mar 31, 2021 at 3:09 PM Geoff Levner <glevner at gmail.com> wrote:
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 -DDLL; 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/20210331/b588ffa0/attachment.html>
- Previous message: [llvm-dev] C++ JIT Compiler with LLVM on Windows 10 - part 5
- Next message: [llvm-dev] Support of Big archive (AIX archive)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]