Fwd: [Bug fortran/12317] New: Incorrect documentation for Fortran debugging features. A patch file follows.

[Andrew Pinski <pinskia at physics dot uc dot edu>]

Forwarding to gcc-patches@ from gcc-bugs@.

Begin forwarded message:

> From: "bugzilla at w170 dot uklinux dot net" <gcc-bugzilla@gcc.gnu.org>
> Date: Wed Sep 17, 2003  5:35:28 AM US/Pacific
> To: gcc-bugs@gcc.gnu.org
> Subject: [Bug fortran/12317] New: Incorrect documentation for Fortran 
> debugging features.  A patch file follows.
> Reply-To: gcc-bugzilla@gcc.gnu.org
>
> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* 
> gcc-bugs@gcc.gnu.org.
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12317
>
>            Summary: Incorrect documentation for Fortran debugging 
> features.
>                     A patch file follows.
>            Product: gcc
>            Version: 3.4
>             Status: UNCONFIRMED
>           Severity: enhancement
>           Priority: P3
>          Component: fortran
>         AssignedTo: unassigned at gcc dot gnu dot org
>         ReportedBy: bugzilla at w170 dot uklinux dot net
>                 CC: gcc-bugs at gcc dot gnu dot org
>
> --- gcc-3.4-20030806/gcc/f/ChangeLog.orig       Thu Jul 31 06:49:13 
> 2003
> +++ gcc-3.4-20030806/gcc/f/ChangeLog    Tue Sep 16 07:07:08 2003
> @@ -1,3 +1,8 @@
> +Tue Sep 16 07:06:00 2003  George Helffrich   <george@geo.titech.ac.jp>
> +
> +        * g77.texi: Remove comment about debugging information for 
> common
> +       blocks not working.
> +
>  Thu Jul 31 01:47:27 2003  Kaveh R. Ghazi  <ghazi@caip.rutgers.edu>
>
>         * com.c (ffecom_init_0): Use `dconsthalf'.
> --- gcc-3.4-20030806/gcc/f/g77.texi.orig        Fri May 16 16:02:19 
> 2003
> +++ gcc-3.4-20030806/gcc/f/g77.texi     Tue Sep 16 07:05:07 2003
> @@ -6900,13 +6900,6 @@
>  is unlikely to ever offer this ability (due to limitations in the
>  C language).
>
> -However, due to apparent bugs in the back end, @command{g77} 
> currently doesn't
> -take advantage of this facility at all---it doesn't emit any debugging
> -information for @code{COMMON} and @code{EQUIVALENCE} areas,
> -other than information
> -on the array of @code{char} it creates (and, in the case
> -of local @code{EQUIVALENCE}, names) for each such area.
> -
>  Yet another example is arrays.
>  @command{g77} represents them to the debugger
>  using the same ``dimensionality'' as in the source code, while 
> @command{f2c}