Lines Matching refs:to
10 * Unless required by applicable law or agreed to in writing, software
18 * JNI method invocation. This is used to call a C/C++ JNI method. The
19 * argument list has to be pushed onto the native stack according to
41 We receive a collection of 32-bit values which correspond to arguments from
42 the interpreter (e.g. float occupies one, double occupies two). It's up to
43 us to convert these into local calling conventions.
49 r0-r3 hold first 4 args to a method
51 r10 (sl) seems to be generally available
67 Happily we don't have to do anything special here -- the args from the
88 @ Standard gcc stack frame setup. We don't need to push the original
90 @ rest of the code. If we don't plan to use a debugger we can speed
96 @ We need to push a variable number of arguments onto the stack.
97 @ Rather than keep a count and pop them off after, we just hold on to
100 @ In theory we don't need to keep sp -- we can do an ldmdb instead of
107 @ argv can't go into r0-r3 because we need to use it to load those.
113 @ No: set r1 to *argv++, and set argc--.
119 @ to the stack. We need to push the last item in argv first, and we
120 @ want the first two items in argv to end up in r2/r3.
124 @ If there are N args, we want to skip 0 and 1, and push (N-1)..2. We
125 @ have N-2 in r3. If we set argv=argv+1, we can count from N-2 to 1
139 @ safe to load two items out of argv even if we're at the end.
145 @ due to instruction prefetching.
157 @ In theory, we need to use the "return type" arg to figure out what
158 @ we have and how to return it. However, unless we have an FPU,
159 @ all we need to do is copy r0-r1 into the JValue union.
