search for: orcx86_64

Hi David, This is really cool. I'd love to get this in-tree. There are two ways we could go about this: (1) Make the OrcArchitecture interface ABI-aware so that it can choose the right resolver code, or (2) Replace the OrcArchitecture classes with OrcABI classes. I.e. We'd just a rename OrcX86_64 -> Orc_X86_64_SysV (and rename I386 & AArch64 similarly) , then we add your code as Orc_X86_64_Windows. I think the second is probably the way to go, with a little refactoring so that the various X86 ABIs could share the stub and resolver code. Any interest in submitting a patch? - Lang....

...rom the jit-compiled module ( which was found by casting the symbol address to the main prototype). Now after some digging I found that the crash is caused by LocalJITCompileCallbackManager::reenter not getting the correct CompileCallback and trampolineid references. This in turn is being caused by OrcX86_64::writeResolverCode not respecting windows calling convention in the asm code for calling the reentry function. After making changes to the asm code in OrcX86_64::writeResolverCode, the code runs without any problems. I thought I share it here with the public so that others who would like to use or...