Lines Matching refs:stack
48 Stack is "full descending". Only the arguments that don't fit in the first 4
49 registers are placed on the stack. "sp" points at the first stacked argument
91 * "export" the PC to the stack frame, f/b/o future exception objects. Must
103 * Given a frame pointer, find the stack save area.
259 * We don't have formal stack frames, so gdb scans upward in the code
262 * got pushed onto the stack. From this it figures out how to restore
263 * the registers, including PC, for the previous stack frame. If gdb
295 /* save stack pointer, add magic word for debuggerd */
347 * Restore the stack pointer and PC from the save point established on entry.
351 * We pushed some registers on the stack in dvmMterpStdRun, then saved
385 /* insert fake function header to help gdb find the stack frame */
7258 * is on the stack. The function's return value is a flag that tells
7276 add sp, sp, #8 @ pop stack
7295 * is on the stack. The function's return value is a flag that tells
7310 add sp, sp, #8 @ pop stack
12606 stack
12668 add sp, sp, #8 @ pop stack
26190 ldr sp, [rSELF,#offThread_jitResumeNSP] @ cut back native stack
26272 ldr sp, [rSELF,#offThread_jitResumeNSP] @ cut back native stack
26636 * As a result, the savedPc in the stack frame will not be wholly accurate. So
26656 SAVEAREA_FROM_FP(r10, rFP) @ r10<- stack save area
26677 SAVEAREA_FROM_FP(r10, rFP) @ r10<- stack save area
26707 SAVEAREA_FROM_FP(r10, rFP) @ r10<- stack save area
26743 @ find space for the new stack frame, check for overflow
26744 SAVEAREA_FROM_FP(r1, rFP) @ r1<- stack save area
26753 blo .LstackOverflow @ yes, this frame will overflow stack
26757 SAVEAREA_FROM_FP(ip, rFP) @ ip<- stack save area
26840 /* insert fake function header to help gdb find the stack frame */
27050 /* fix earlier stack overflow if necessary; may trash rFP */
27064 add sp, sp, #8 @ restore stack
27100 /* fix stack overflow if necessary */
27250 * registers for EABI 64-bit stack alignment.)
