Displaying 2 results from an estimated 2 matches for "42194c".
Did you mean:
421934c
2017 Jan 31
2
llvm.read_register for %RIP on x86_64
On Tue, Jan 31, 2017 at 3:11 PM, Renato Golin <renato.golin at linaro.org>
wrote:
> On 31 Jan 2017 8:58 p.m., "Kostya Serebryany" <kcc at google.com> wrote:
>
> hmm. I am not sure I understood you. The last two paragraphs seem to
> contradict each other.
> So, you recommend to extend read_register to read the PC, or
> "read_register is locked at the
2017 Jan 31
0
llvm.read_register for %RIP on x86_64
On 31 Jan 2017 8:58 p.m., "Kostya Serebryany" <kcc at google.com> wrote:
hmm. I am not sure I understood you. The last two paragraphs seem to
contradict each other.
So, you recommend to extend read_register to read the PC, or
"read_register is locked at the stack pointer as a design decision"?
Both. :-)
There was a design decision to only support SP because we had no