Use a register spec for StoreIC and KeyedStoreIC.

Use a register spec for StoreIC and KeyedStoreIC.

This continues refactoring already applied for LoadIC in r22035 (https://code.google.com/p/v8/source/detail?r=22035).

R=jkummerow@chromium.org

Committed: https://code.google.com/p/v8/source/detail?r=22328

[mvstanton, 2014-07-10 11:50:02]

Hi Jakob,
Here is the refactoring we talked about. Thx for the look!
--Michael

[Jakob Kummerow, 2014-07-10 13:42:06]

LGTM. 

I less than three this!

https://codereview.chromium.org/381633002/diff/60001/src/ia32/ic-ia32.cc
File src/ia32/ic-ia32.cc (right):

https://codereview.chromium.org/381633002/diff/60001/src/ia32/ic-ia32.cc#newc...
src/ia32/ic-ia32.cc:970: static void LoadIC_PushArgs(MacroAssembler* masm) {
Nice idea!

https://codereview.chromium.org/381633002/diff/60001/src/ia32/ic-ia32.cc#newc...
src/ia32/ic-ia32.cc:1022: const Register StoreIC::ReceiverRegister() { return
edx; }
I guess the next CL will s/edx/LoadIC::ReceiverRegister()/ here?

https://codereview.chromium.org/381633002/diff/60001/src/ia32/lithium-codegen...
File src/ia32/lithium-codegen-ia32.cc (right):

https://codereview.chromium.org/381633002/diff/60001/src/ia32/lithium-codegen...
src/ia32/lithium-codegen-ia32.cc:4061: // Is this a problem?
Nope. We're calling out, so the entire instruction is (hopefully!) marked as a
call, so the register allocator considers all registers trashed anyway. Having
it put receiver and value in the registers that the stub expects is just an
optimization. The name however is a constant, so we can just put it in manually.

https://codereview.chromium.org/381633002/diff/60001/src/x64/ic-x64.cc
File src/x64/ic-x64.cc (right):

https://codereview.chromium.org/381633002/diff/60001/src/x64/ic-x64.cc#newcod...
src/x64/ic-x64.cc:903: // ----------- S t a t e -------------
just "// The return address is on the stack."

[mvstanton, 2014-07-10 15:00:22]

Committed patchset #3 manually as r22328.