It seems weird now, but natural at time. Point a register at the data following the call, rely on the caller advancing over the argument and jumping back to the (presumed) code after the data. The stack isn't involved at all...

Edit: found this on the 'net:-

https://retrocomputing.stackexchange.com/questions/9328/does...