dwarf2out_frame_init broken

Jeffrey A Law law@cygnus.com
Mon Feb 2 10:28:00 GMT 1998


  In message < vyzzpkauxox.fsf@issan.informatik.uni-dortmund.de >you write:
  > Even if DWARF2_UNWIND_INFO is defined to zero the user can still force
  > dwarf2 unwind information instead of setjmp with -fno-sjlj-exceptions.
  > Thus dwarf2out_frame_init must still call dwarf2out_def_cfa and
  > initial_return_save in that case.  This makes it consistent with
  > dwarf2out_frame_finish.  Note that dwarf2out_frame_init is only called
  > when dwarf2out_do_frame returns nonzero.
  > 
  > 
  > 1998-01-30  Andreas Schwab  <schwab@issan.informatik.uni-dortmund.de>
  > 
  > 	* dwarf2out.c (dwarf2out_frame_init): Undo last change, so that
  > 	-fno-sjlj-exceptions works for a target that defines
  > 	DWARF2_UNWIND_INFO as zero.
I've installed this patch.  jfc -- in theory, defining DWARF2_UNWIND_INFO
to zero in sni.h should have stopped it from outputting anything in
default case.  Can you verify that things still work?  If not we'll
have to track down what routine is actually outputting dwarf2 records
instead of trying to catch it in dwarf2out_frame_init.

jeff



More information about the Gcc mailing list