Displaying 2 results from an estimated 2 matches for "resolver_entry".
2016 May 04
2
OrcLazyJIT for windows
...ib/ExecutionEngine/Orc/OrcAchitectureSupport.cpp with the following.
Note that more work is needed to both support linux/windows but I am not
sure how this is best dealt with in llvm.
// windows (arguments go to rcx and rdx and have reversed order)---
const uint8_t ResolverCode[] = {
// resolver_entry:
0x55, // 0x00: pushq %rbp
0x48, 0x89, 0xe5, // 0x01: movq %rsp, %rbp
0x50, // 0x04: pushq %rax
0x53, // 0x05: pushq %rbx
0x51,...
2016 May 04
2
OrcLazyJIT for windows
...Note that more work is needed to both support linux/windows but I am not
>> sure how this is best dealt with in llvm.
>>
>>
>> // windows (arguments go to rcx and rdx and have reversed order)---
>>
>> const uint8_t ResolverCode[] = {
>>
>> // resolver_entry:
>>
>> 0x55, // 0x00: pushq %rbp
>>
>> 0x48, 0x89, 0xe5, // 0x01: movq %rsp, %rbp
>>
>> 0x50, // 0x04: pushq %rax
>>
>> 0x53,...