Debug formats on Linux

[mrs@wrs.com]

> Date: Sun, 29 Oct 2000 13:36:18 +0100
> From: Toon Moene <toon@moene.indiv.nluug.nl>
> To: "Joseph S. Myers" <jsm28@cam.ac.uk>
> CC: Mark Mitchell <mark@codesourcery.com>, gcc@gcc.gnu.org

> Joseph S. Myers wrote:

> > FAIL: g77.f-torture/compile/20000511-2.f,  -O3 -g
> > FAIL: g77.f-torture/compile/20000629-1.f,  -O3 -g
> > FAIL: g77.f-torture/compile/980310-3.f,  -O3 -g
> > FAIL: g77.f-torture/compile/980310-4.f,  -O3 -g
> > FAIL: g77.f-torture/compile/980310-7.f,  -O3 -g
> > FAIL: g77.f-torture/execute/19981119-0.f compilation,  -O3 -g
> > FAIL: g77.f-torture/execute/auto0.f compilation,  -O3 -g
> > FAIL: g77.f-torture/execute/auto1.f compilation,  -O3 -g
> > (all ICE at dwarf2out.c:8114 (add_bound_info))

> > These can be tested without the patch by compiling the individual
> > testcases with -gdwarf-2 -O3; perhaps someone understanding Fortran
> > and g77 could look at why those Fortran cases crash and whether the
> > problem is with the Fortran front end or in the DWARF2 support.

Please try the below patch, and if it makes things work better...
we can try and get it in.

Doing diffs in dwarf2out.c.~1~:
*** dwarf2out.c.~1~	Mon Oct 30 11:16:19 2000
--- dwarf2out.c	Mon Oct 30 11:17:23 2000
*************** add_bound_info (subrange_die, bound_attr
*** 8106,8111 ****
--- 8106,8112 ----
      case VAR_DECL:
      case COMPONENT_REF:
      case COND_EXPR:
+     case INDIRECT_REF:
        /* ??? These types of bounds can be created by the Ada front end,
  	 and it isn't clear how to emit debug info for them.  */
        break;
--------------