X-Git-Url: http://git.sourceforge.jp/view?a=blobdiff_plain;f=gcc%2Fdwarf2out.c;h=866108022af884d5094afc7b29fcde390c824d91;hb=e965e3405db23b8c3293cbad110961a42291a53f;hp=4c350ebd7c19835d26514ca55abef2ce82c17e29;hpb=51befc2ecd438e38e5eb6032d3431fc15cd00932;p=pf3gnuchains%2Fgcc-fork.git

diff --git a/gcc/dwarf2out.c b/gcc/dwarf2out.c
index 4c350ebd7c1..866108022af 100644
--- a/gcc/dwarf2out.c
+++ b/gcc/dwarf2out.c
@@ -1829,6 +1829,14 @@ output_call_frame_info (for_eh)
       fputc ('\n', asm_out_file);
       ASM_OUTPUT_LABEL (asm_out_file, l1);
 
+      /* ??? This always emits a 4 byte offset when for_eh is true, but it
+	 emits a target dependent sized offset when for_eh is not true.
+	 This inconsistency may confuse gdb.  The only case where we need a
+	 non-4 byte offset is for the Irix6 N64 ABI, so we may lose SGI
+	 compatibility if we emit a 4 byte offset.  We need a 4 byte offset
+	 though in order to be compatible with the dwarf_fde struct in frame.c.
+	 If the for_eh case is changed, then the struct in frame.c has
+	 to be adjusted appropriately.  */
       if (for_eh)
 	ASM_OUTPUT_DWARF_DELTA4 (asm_out_file, l1, "__FRAME_BEGIN__");
       else