Displaying 3 results from an estimated 3 matches for "8a562219".
Did you mean:
8a26221a
2016 Jul 29
1
XRay: Demo on x86_64/Linux almost done; some questions.
...e help I can get to make XRay work on ARM too.
>
Yes, I am trying to port XRay on LLVM to ARM, but I'm just starting with
LLVM.
>
> Cheers!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160729/8a562219/attachment.html>
2016 Jul 29
0
XRay: Demo on x86_64/Linux almost done; some questions.
> On 29 Jul 2016, at 09:14, Serge Rogatch via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>
> Hello,
>
> Can I ask you why you chose to patch both function entrances and exits, rather than just patching the entrances and (in the patches) pushing on the stack the address of __xray_FunctionExit , so that the user function returns normally (with RETQ or POP RIP or whatever
2016 Jul 28
4
XRay: Demo on x86_64/Linux almost done; some questions.
Hello,
Can I ask you why you chose to patch both function entrances and exits,
rather than just patching the entrances and (in the patches) pushing on the
stack the address of __xray_FunctionExit , so that the user function
returns normally (with RETQ or POP RIP or whatever else instruction) rather
than jumping into __xray_FunctionExit?
By patching just the function entrances, you avoid