- treat REGT_STRING | REGT_ADDROF just like REGT_STRING for direct native functions.

Both pass a reference so there's no need to treat them differently.
This commit is contained in:
Christoph Oelckers 2018-12-04 18:21:00 +01:00
parent 062528e0e2
commit de9805d5c7

View file

@ -356,6 +356,7 @@ void JitCompiler::EmitNativeCall(VMNativeFunction *target)
case REGT_INT | REGT_KONST:
call->setArg(slot, imm(konstd[bc]));
break;
case REGT_STRING | REGT_ADDROF: // AddrOf string is essentially the same - a reference to the register, just not constant on the receiving side.
case REGT_STRING:
call->setArg(slot, regS[bc]);
break;
@ -393,7 +394,6 @@ void JitCompiler::EmitNativeCall(VMNativeFunction *target)
call->setArg(slot, tmp2);
break;
case REGT_STRING | REGT_ADDROF:
case REGT_INT | REGT_ADDROF:
case REGT_POINTER | REGT_ADDROF:
case REGT_FLOAT | REGT_ADDROF: