Andrew Cagney wrote:
> Can I suggest pulling the error() and internal_error() message changes 
> out, cleaning them up, and then committing them separatly.   Better 
> messages (eg printing the reason for a bad switch) are always a good idea.
> 
> That also has the benefit of trimming your patch back.

Well, this is the patch without unrelated message changes. Can I commit 
it? It seems to be quite stable in our everyday use...

2002-05-31  Michal Ludvig  <mludvig@suse.cz>

         * dwarf2cfi.c (dwarf_frame_buffer): Delete.
         (read_encoded_pointer): Add new argument,
         warn on indirect pointers.
         (execute_cfa_program): Warn on relative addressing.
         (dwarf2_build_frame_info): Only call parse_frame_info
         for .debug_frame and .eh_frame.
         (parse_frame_info): New, derived from dwarf2_build_frame_info,
         fixed augmentation handling, added relative addressing,
         ignore duplicate FDEs. Added comments.

Michal Ludvig
-- 
* SuSE CR, s.r.o     * mludvig@suse.cz
* +420 2 9654 5373   * http://www.suse.cz