From b3e3732ce16b9c87e89774592c29e81ed13db236 Mon Sep 17 00:00:00 2001 From: George Helffrich Date: Sun, 21 Sep 2003 13:26:36 +0000 Subject: [PATCH] g77.texi: Remove ancient part about debugging COMMON and EQUIVALENCE not correctly. 2003-09-21 George Helffrich * g77.texi: Remove ancient part about debugging COMMON and EQUIVALENCE not correctly. From-SVN: r71623 --- gcc/f/ChangeLog | 5 +++++ gcc/f/g77.texi | 7 ------- 2 files changed, 5 insertions(+), 7 deletions(-) diff --git a/gcc/f/ChangeLog b/gcc/f/ChangeLog index 73d2a42ad36..e6f71016fae 100644 --- a/gcc/f/ChangeLog +++ b/gcc/f/ChangeLog @@ -1,3 +1,8 @@ +2003-09-21 George Helffrich + + * g77.texi: Remove ancient part about debugging COMMON + and EQUIVALENCE not correctly. + 2003-09-18 Roger Sayle * com.c (ffecom_overlap_): Remove FFS_EXPR case. diff --git a/gcc/f/g77.texi b/gcc/f/g77.texi index 03f6a6a3afb..8eda9a9f457 100644 --- a/gcc/f/g77.texi +++ b/gcc/f/g77.texi @@ -6900,13 +6900,6 @@ without having to traverse C-like structures and unions, while @command{f2c} 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} -- 2.30.2