- treat REGT_STRING | REGT_ADDROF just like REGT_STRING for direct na…

…tive functions. Both pass a reference so there's no need to treat them differently.
ZDoom · Dec 4, 2018 · de9805d · de9805d
1 parent 062528e
commit de9805d
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/src/scripting/vm/jit_call.cpp b/src/scripting/vm/jit_call.cpp
@@ -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: