Displaying 2 results from an estimated 2 matches for "move_immediate".
Did you mean:
mo_immediate
2015 Jul 09
5
[LLVMdev] [RFC] New StackMap format proposal (StackMap v2)
...atch over all reserved bytes.
The alternative would be for LLVM to emit the call at the end and record just the size of the call instruction encoding. That seems like a silly, x86-specific waste of stackmap space though. The JIT can either do the encoding and keep track of the info, or a small nop+move_immediate decoder can figure it out for all reasonable cases.
Andy
>
> Thanks,
> Swaroop.
>
> From: Juergen Ributzka [mailto:juergen at apple.com]
> Sent: Thursday, July 9, 2015 2:04 PM
> To: LLVM Dev
> Cc: Lang Hames; Andrew Trick; Phil Pizlo; Philip Reames; Sanjoy Das; Swaroo...
2015 Jul 09
9
[LLVMdev] [RFC] New StackMap format proposal (StackMap v2)
Hi @ll,
over the past year we gained more experience with the patchpoint/stackmap/statepoint intrinsics and it exposed limitations in the stackmap format.
The following proposal includes feedback and request from several interested parties and I would like to hear your feedback.
Missing correlation between functions and stackmap records:
Originally the client had to keep track of the ID to know