[patch RFC] Re: Notes on a frame_unwind_address_in_block problem

[Daniel Jacobowitz]

On Tue, Feb 20, 2007 at 10:31:26AM -0500, Daniel Jacobowitz wrote:
> Hmm, one small additional downside: it sends the *_FRAME constants out
> into dozens of new files.  I was poking at adding a new one, which
> requires auditing all of the existing uses, which has now gotten much
> harder.

Bah, ignore this.  For anyone else who wants to audit frame types: in
most cases it suffices to inside frame.c search for ->type, and
outside it search for get_frame_type.  There are no interfaces which
pass a frame type to a function, except for the two new ones in
frame.c, so this finds everything interesting.

-- 
Daniel Jacobowitz
CodeSourcery