Chromium Code Reviews| Index: src/regexp/mips64/regexp-macro-assembler-mips64.cc |
| diff --git a/src/regexp/mips64/regexp-macro-assembler-mips64.cc b/src/regexp/mips64/regexp-macro-assembler-mips64.cc |
| index dff4b79f78ac85cf308597a594e4a9bc95d66181..bf95a9c97ff70e141990c4eab47edd9d71cad813 100644 |
| --- a/src/regexp/mips64/regexp-macro-assembler-mips64.cc |
| +++ b/src/regexp/mips64/regexp-macro-assembler-mips64.cc |
| @@ -671,10 +671,7 @@ Handle<HeapObject> RegExpMacroAssemblerMIPS::GetCode(Handle<String> source) { |
| s3.bit() | s4.bit() | s5.bit() | s6.bit() | s7.bit() | fp.bit(); |
| RegList argument_registers = a0.bit() | a1.bit() | a2.bit() | a3.bit(); |
| - if (kMipsAbi == kN64) { |
| - // TODO(plind): Should probably alias a4-a7, for clarity. |
| - argument_registers |= a4.bit() | a5.bit() | a6.bit() | a7.bit(); |
| - } |
| + argument_registers |= a4.bit() | a5.bit() | a6.bit() | a7.bit(); |
|
balazs.kilvady
2016/01/28 12:48:22
I think a4-a7 bits could be 'or'-ed to the above l
Ilija.Pavlovic1
2016/01/28 15:07:30
Yes, you are right. I didn't noted that definition
|
| __ MultiPush(argument_registers | registers_to_retain | ra.bit()); |
| // Set frame pointer in space for it if this is not a direct call |