public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* RFC: Thumb and unwind information
@ 2004-01-09 21:20 Daniel Jacobowitz
  0 siblings, 0 replies; only message in thread
From: Daniel Jacobowitz @ 2004-01-09 21:20 UTC (permalink / raw)
  To: gcc

Some time ago, Richard Earnshaw pointed out to me that we generate no useful
.debug_frame information for Thumb.  The basic reason is that the
interesting portions of the prologues and epilogues are still emitted as
text.  Thumb prologues can be, to say the least, complicated.

I'm going to try my hand at fixing this.  I see two ways:
  - Emit more of this as RTL.
  - Emit it as an unspec and generate an RTX_FRAME_RELATED_EXPR
    SEQUENCE that describes it well enough for the unwind information.

I don't know if the former would have major benefits.  It would definitely
be complicated, scheduling opportunity would be minimal, and the extra RTL
would presumably slow down GCC.  The latter would be simpler.  I think the
only major change it will require will be support for labels in the
SEQUENCE to indicate that not everything happens all at once at the end of
the prologue.  This could also be used to fix unwind information for ARM
multi-instruction returns when a single ldmia can't be used.

Thoughts?

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2004-01-09 21:20 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-01-09 21:20 RFC: Thumb and unwind information Daniel Jacobowitz

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).