Lines Matching refs:stack

238 Then, you must also make sure to allocate extra space on the stack for
240 space is to be allocated over and above the actual stack space required
245 specifies the amount of extra space to be added on to the stack to allow
247 E.g. if your task requires 2000 bytes of stack space, you must allocate
248 (2000 + XT_STACK_EXTRA_CLIB) bytes for the stack.
302 stack. Each task needs enough space for its own use, its own interrupt
303 stack frame (defined in xtensa_context.h) and space to save coprocessor
304 state, if any. Several factors influence the size of the stack required,
307 stack space. The tool xt-stack-usage is helpful in determining safe stack
310 Some macros are provided in xtensa_config.h to help determine the stack
312 basis for each task's stack size. They are minimum requirements taking
318 defines the minimum stack size for any task. Be very careful if you try
319 to use a stack size smaller than this minimum. Stack overruns can cause
321 FreeRTOS stack checking features during development.
323 WARNING: The newlib printf() function uses a lot of stack space. Be very
326 and uses far less stack space. More information about this library is in
333 Beginning with port version 1.2, the port uses a separate interrupt stack
335 reserve space on its stack to handle interrupts. The size of the interrupt
336 stack is controlled by the parameter "configISR_STACK_SIZE" defined in
437     a1      = stack pointer (alias sp)
441               stack. Details are in the Xtensa Tools manuals.
447 window need to be spilled to preallocated space in the stack frame, or
455     a1      = stack pointer (alias sp)
459               stack. Details are in the Xtensa Tools manuals.
486 The saved context stack frames for context switches that occur as
490 of stack frames. The top of the suspended task's stack is pointed to
491 by pxCurrentTCB->pxTopOfStack. A special location common to both stack
492 frames differentiates solicited and interrupt stack frames.
500 -O0 costs performance and usually also increases stack usage. To make
514 function, and also allows the debugger's stack trace to show the correct
573 bounds on interrupt latency (for a given priority) and stack depth.
600     Having allocated the exception stack frame, the user exception handler
678     space on top of the stack. Because the window hardware may have
680     stack pointer, it is necessary to protect those values. The alloca
691     on the caller's stack. The handler does exactly that, and skips