Use .cfi to make it actually fairly readable... at least, if you know what any
of the cfi commands are.
Some subtleties:
EVERY ISR should have one of 'push_fake_status_code' and
'intel_pushes_status_code', in addition to both 'isr_prologue' and
'isr_epilogue'
Some things in isr-asm.s are 'signal handlers' and some are not; this is
totally independent from whether Intel pushes a status code or not.
com_print_backtrace needs to know whether its starting address is one that's
"signal-handler-ish" or not; but you can only run it by 'call'ing, so it
clearly is not signal-handler-ish.
'idle' has been moved to assembly, mostly so that we don't uselessly try and
unwind through it.
gsilvis
commented
5 years ago
Use .cfi to make it actually fairly readable... at least, if you know what any of the cfi commands are.
Some subtleties: