Re: Debug formats on Linux

[Toon Moene <toon at moene dot indiv dot nluug dot nl>]

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.

The Fortran failures are due to the fact that add_bound_info (in
dwarf2out.c) doesn't handle INDIRECT_REF as a bound tree code.  I do not
know enough about this to decide whether this use of INDIRECT_REF is
correct or not.  If it is harmless, we could start by adding it to the
list of codes emitted by Ada, and ignored by dwarf2out.c:

    case MAX_EXPR:
    case VAR_DECL:
    case COMPONENT_REF:
    case COND_EXPR:
      /* ??? 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;

Cheers,

-- 
Toon Moene - mailto:toon@moene.indiv.nluug.nl - phoneto: +31 346 214290
Saturnushof 14, 3738 XG  Maartensdijk, The Netherlands
GNU Fortran 77: http://gcc.gnu.org/onlinedocs/g77_news.html
GNU Fortran 95: http://g95.sourceforge.net/ (under construction)