This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
DWARF2 fix for Fortran
- To: gcc-patches at gcc dot gnu dot org
- Subject: DWARF2 fix for Fortran
- From: Mike Stump <mrs at windriver dot com>
- Date: Tue, 31 Oct 2000 11:01:04 -0800 (PST)
Without the below the compiler does this:
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)
when running the Fortran testsuite on a DWARF2 system. In order to
move to DWARF2, we need for it to be as good as stabs. The below
patch cures these problems. This was discussed and tested on the gcc
list.
* dwarf2.out.c (add_bound_info): Handle Fortran better.
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;
--------------