I’m using the LLVM for a JIT-Client under Windows 64bit. I tried various stuff with it and noticed, that object files or libraries which are generated by the Visual Studio Compiler 2015 or 2017 will break the jitted code, when they are added to the process.
I opened a bug for this a while ago (https://bugs.llvm.org/show_bug.cgi?id=39447) – sadly this bug will become a stopper for me… So I wanted to ask for advice:
Does anyone know anything about this bug or a similar one? Does anyone have an idea about this? Is this bug maybe a duplication with another bug?
I’m still a beginner, so I hope I did everything right >o<
I think it would be helpful to provide some more of the assembly you are ending up with. In the example below: Which source code are you compiling? What does it try to achieve? What happens to eax, ebx, rdi after the xor?
+Andy,Zachary: Maybe you can correct, verify or explain in more detail my analysis in the end of this mail. I have no internal knowledge whatsoever, I just happened to reverse engineer this some time ago.
From what I found in the old thread and in your bug report, I can make a guess.
I show you a short snippet of the assembly output.
mov eax, DWORD PTR ?myInt@@3HA ; myInt
lea rdi, OFFSET FLAT:__ImageBase
xor ebx, ebx
Then these offset is used to jump to some labels like "$[LL4 at execute](http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev):".
The $LL4 looks like a symbol name in a jump table. There are a few examples (in the context of an unrelated bug report), that show how such tables look like: Here is an explanation of LEA: Reid gave an important hint here already: dllimport symbols. MSVC apparently still assumes a small code model and uses 32 bit relocations. (Maybe you could change that nowadays with a compiler flag or so?) Have a look at this thread from 2015: Quoting Andy Ayers: I guess this is the missing piece in your case. You have to do this patching step yourself, that would otherwise happen magically in the Microsoft linker (resolve relocation to a load-time jump stub) and loader (create/fill jump stub with the actual DLL symbol address), because the MSVC compiler assumes it when creating your obj file (creates the relocation for a base address, adds the offset and calls it). If this is the case, you should encounter __imp_foo symbol relocations. I don’t remember the exact details, but this is what you want to watch out for. What needs to happen, conceptually, is something like this: __ImageBase is the address of a table that you create and OFFSET FLAT is a relative offset to the entry that you need to prepare. The entry must NOT store the target addresses (to be loaded and called), BUT a jump stub/trampoline like “jmp 0x00000000” (which forwards execution to the actual call target). When you resolve the relocation for the import symbol (__imp_foo) to the jump stub, you probably don’t know the jmp target right away. So, you can leave it nulled and emit a new relocation to fill out the address (symbol foo). Depending on how your stub works, it may be a relative offset or a 64-bit absolute address. In the end your code calls the jump stub address as if it was the actual target function. IIRC you cannot simply resolve the original relocation to the target, even if you know it already, because the code emitted by MSVC has the base+offset calculation already built in. There are some pretty useful tools for all that in LLVM Orc: Cheers Stefan
I provided the .cpp file, the .obj file and the .cod file in the attachments at the bug report (https://bugs.llvm.org/show_bug.cgi?id=39447)
The .cod file is what you are looking for. I remember talking with you about that bug :’D
But I’m just a beginner >o<