Re: [rfc] trad-frame change

[Andrew Cagney <cagney@gnu.org>]

> Sounds pretty nice to me.  For what it's worth, I'm testing a sigtramp
> unwinder on MIPS/Linux that could almost but not quite use this:
> 
> +struct mips_prologue_cache
> +{
> +  /* The stack pointer at the time this frame was created; i.e. the
> +     caller's stack pointer when this function was called.  It is used
> +     to identify this frame.  */
> +  CORE_ADDR prev_sp;
> +
> +  CORE_ADDR tramp_start;
> +
> +  int kind;
> +
> +  /* Saved register offsets.  */
> +  struct trad_frame_saved_reg *saved_regs;
> +};
> 
> (so that the frame ID is constant for both instructions of the
> trampoline).

.. and frame_id_unwind() looks something like:

	frame_id_build (cache->prev_sp, cache->tramp_start)?

the trad-frame chache instead has the field:

     struct frame_id this_id;

which is equivalent - the ID being constructed up front.

What is "kind"?

Andrew