Fix 24 powerpc-ibm-aix4.1 gdb testsuite failures due to bad gcc debug info.

	* xcoffout.c (xcoffout_begin_function): Call xcoffout_block for
	the zero'th block.


git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@20882 138bc75d-0d04-0410-961f-82ee72b054a4

1 files changed, 10 insertions, 0 deletions

diff --git a/gcc/xcoffout.c b/gcc/xcoffout.c
index ebbd9c6c4ff..baa0cd2ed01 100644
--- a/gcc/xcoffout.c
+++ b/gcc/xcoffout.c
@@ -500,6 +500,16 @@ xcoffout_begin_function (file, last_linenum)
 {
   ASM_OUTPUT_LFB (file, last_linenum);
   dbxout_parms (DECL_ARGUMENTS (current_function_decl));
+
+  /* Emit the symbols for the outermost BLOCK's variables.  sdbout.c does this
+     in sdbout_begin_block, but there is no guarantee that there will be any
+     inner block 1, so we must do it here.  This gives a result similar to
+     dbxout, so it does make some sense.  */
+  do_block = 0;
+  next_block_number = 0;
+  xcoffout_block (DECL_INITIAL (current_function_decl), 0,
+		  DECL_ARGUMENTS (current_function_decl));
+
   ASM_OUTPUT_SOURCE_LINE (file, last_linenum);
 }