https://codereview.chromium.org/209933003/diff/1/src/arm64/lithium-codegen-arm64.h
File src/arm64/lithium-codegen-arm64.h (right):
https://codereview.chromium.org/209933003/diff/1/src/arm64/lithium-codegen-arm64.h#newcode385
src/arm64/lithium-codegen-arm64.h:385:
codegen_->masm_->Mov(to_be_pushed_lr, lr);
On 2014/03/24 11:16:59, vincent.belliard.arm wrote:
On 2014/03/24 11:09:25, ulan wrote:
> to_be_pushed_lr is ip0, how do we guarantee that this doesn't get
clobbered
from
> this point until the StoreRegistersStateStub gets control?
This register is reserved by the UseScratchRegisterScope so it cannot
be used by
the call (which will use the next register: ip1).
After the call, we jump directly to the stub code (which has its own
context)
which starts also by a UseScratchRegisterScope which also reserves
to_be_pushed_lr.
Right, and what if the ip0 is not available in the current scope because
it was already reserved before PushSafepointRegistersScope?
https://codereview.chromium.org/209933003/
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
