[patch/rfc] frame->register_unwind() - different way of unwinding a frame

[Andrew Cagney]

I've checked this in.

At present it doesn't directly affect any targets.  It could, however, 
affect the output of ``info frame'' (although it shouldn't).

Andrew


> FYI,
> 
> I've now managed to test this on i386 GNU/Linux, ARM various embedded sim targets, and PPC/NetBSD (with the new mechanism enabled).
> 
> I think the ->register_unwind() change is sufficently in the correct direction to commit this.
> 
> Any thoughts?  I'll look to commit in a week.
> A follow-on patch will then make it the default.
> 
> Andrew 
> 2002-04-20  Andrew Cagney  <ac131313@redhat.com>
> 
> 	* stack.c (frame_info): Use frame_register_unwind instead of
> 	saved_regs.  Mention when the SP is on the stack or in a register.
> 
> 	* frame.h (frame_register_unwind_ftype): Define.  Document.
> 	(struct frame_info): Add field register_unwind and
> 	register_unwind_cache.
> 	(frame_register_unwind): Declare.
> 	(generic_unwind_get_saved_register): Declare.
> 
> 	* frame.c (frame_register_unwind): New function.
> 	(generic_unwind_get_saved_register): New function.
> 
> 	* blockframe.c (generic_call_dummy_register_unwind): New function.
> 	(frame_saved_regs_register_unwind): New function.
> 	(set_unwind_by_pc): New function.
> 	(create_new_frame): New function.
> 	(get_prev_frame): New function.
>