On 06/29/2011 04:01 PM, Steven Bosscher wrote:
> How many TARGET_ASM_FUNCTION_{PRO,EPI}LOGUE targets are left anyway?
Answering the question that it sounds like you actually asked: 2 or 3.
Not that it does us that much good because of the other uses.
FWIW, Alpha appears to be the only target that (ab)uses
ASM_DECLARE_FUNCTION_NAME to output unwind info. That might have been
a mistake, considering the interference that causes with using elfos.h.
I'm not sure what all the zeroing of backend variables that several
targets are doing is for. Better GC at the end of the function maybe?
r~
----------------------
Users of TARGET_ASM_FUNCTION_PROLOGUE
Outputs the real prologue
pdp11
rs6000 if !TARGET_SCHED_PROLOG
Outputs assembly comments
arm
m32r
mep
picochip
rx
Outputs unwind info
ia64 (.regstk, .prologue)
microblaze (.ent, .frame, .mask)
mips (.ent, .frame, .mask)
pa (.PROC and .CALLINFO)
score (.ent, .frame, .mask)
Other
frv renaming of gr3?, frv_pack_insns
mips mips16 function stub, gp load at function start
microblaze add _interrupt_handler alias?
mmix init register renaming?
rs6000 emit .extern as needed before uses?
sparc emit .register as needed
Users of TARGET_ASM_FUNCTION_EPILOGUE
Outputs the real epilogue
arm thumb1 only
pdp11
rs6000 if !TARGET_SCHED_PROLOG
Outputs assembly comments
picochip
mmix actually just a newline?
Outputs unwind info
microblaze (.end)
mips (.end)
pa (.PROCEND and stuff)
rs6000 aix traceback table
score (.end)
Other
arm validate some frame offsets?
frv reset variables
i386 undo pic register renaming, darwin nop hack
ia64 undo register renaming
m32r reset variables
microblaze finish _interrupt_handler alias, reset variables
mips undo pic register renaming
rs6000 darwin branch islands
sh reset variables
sparc unwind nop, deferred case vectors
xtensa reset variables
