Searched refs:epilogue (Results 1 – 10 of 10) sorted by relevance
| /linux-4.1.27/arch/x86/crypto/ |
| D | aes-x86_64-asm_64.S | 73 #define epilogue(FUNC,r1,r2,r3,r4,r5,r6,r7,r8,r9) \ macro
136 #define return(FUNC) epilogue(FUNC,R8,R2,R9,R7,R5,R6,R3,R4,R11)
|
| /linux-4.1.27/arch/sh/kernel/cpu/sh5/ |
| D | switchto.S | 188 ! epilogue
|
| /linux-4.1.27/arch/frv/kernel/ |
| D | break.S | 123 # handle BREAK instruction in kernel-mode exception epilogue
|
| /linux-4.1.27/Documentation/metag/ |
| D | kernel-ABI.txt | 232 example of a frame pointer epilogue:
|
| /linux-4.1.27/arch/cris/arch-v32/kernel/ |
| D | entry.S | 243 ;; This epilogue MUST match the prologues in multiple_interrupt, irq.h
|
| /linux-4.1.27/arch/cris/arch-v10/kernel/ |
| D | entry.S | 200 ;; this epilogue MUST match the prologues in multiple_interrupt, irq.h and ptregs.h
|
| /linux-4.1.27/Documentation/trace/ |
| D | ftrace-design.txt | 171 code. Since you are returning from a function (after the epilogue), you might
|
| /linux-4.1.27/arch/arm/crypto/ |
| D | sha1-armv4-large.S | 31 @ performance is affected by prologue and epilogue overhead,
|
| /linux-4.1.27/Documentation/s390/ |
| D | Debugging390.txt | 442 epilogue:
615 # Function epilogue below
664 # compiler adds 1 extra instruction to epilogue this is done to
|
| /linux-4.1.27/Documentation/networking/ |
| D | filter.txt | 785 Prologue and epilogue are emitted by JIT and are implicit in the
|