Next: Stack Smashing Protection, Previous: Tail Calls, Up: Stack and Calling [Contents][Index]
The prologue may perform a variety of target dependent tasks such as saving callee-saved registers, saving the return address, aligning the stack, creating a stack frame, initializing the PIC register, setting up the static chain, etc.
On some targets some of these tasks may be independent of others and thus may be shrink-wrapped separately. These independent tasks are referred to as components and are handled generically by the target independent parts of GCC.
Using the following hooks those prologue or epilogue components can be shrink-wrapped separately, so that the initialization (and possibly teardown) those components do is not done as frequently on execution paths where this would unnecessary.
What exactly those components are is up to the target code; the generic
code treats them abstractly, as a bit in an sbitmap
. These
sbitmap
s are allocated by the shrink_wrap.get_separate_components
and shrink_wrap.components_for_bb
hooks, and deallocated by the
generic code.
This hook should return an sbitmap
with the bits set for those
components that can be separately shrink-wrapped in the current function.
Return NULL
if the current function should not get any separate
shrink-wrapping.
Don’t define this hook if it would always return NULL
.
If it is defined, the other hooks in this group have to be defined as well.
This hook should return an sbitmap
with the bits set for those
components where either the prologue component has to be executed before
the basic_block
, or the epilogue component after it, or both.
This hook should clear the bits in the components bitmap for those components in edge_components that the target cannot handle on edge e, where is_prologue says if this is for a prologue or an epilogue instead.
Emit prologue insns for the components indicated by the parameter.
Emit epilogue insns for the components indicated by the parameter.
Mark the components in the parameter as handled, so that the
prologue
and epilogue
named patterns know to ignore those
components. The target code should not hang on to the sbitmap
, it
will be deleted after this call.
Next: Stack Smashing Protection, Previous: Tail Calls, Up: Stack and Calling [Contents][Index]