This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: g77/gdb problem
- To: craig at jcb-sc dot com
- Subject: Re: g77/gdb problem
- From: Toon Moene <toon at moene dot indiv dot nluug dot nl>
- Date: Sun, 05 Sep 1999 22:37:36 +0200
- CC: rth at cygnus dot com, andy at ociw dot edu, gcc-bugs at gcc dot gnu dot org
- Organization: Moene Computational Physics, Maartensdijk, The Netherlands
- References: <199908030114.SAA14779@fluff.ociw.edu> <37A739CA.D5FF01D9@moene.indiv.nluug.nl> <19990807184733.B20667@cygnus.com> <19990905184253.6478.qmail@deer>
craig@jcb-sc.com wrote:
[ Debugging info for COMMON variables in the light of:
SUBROUTINE AAP(NOOT)
REAL NOOT(MIES)
COMMON /WIM/ ZUS, JET, MIES, TEUN
where the extent of array NOOT is passed in COMMON "WIM" (item MIES)
and another routine can legally declare "WIM" as:
DOUBLE PRECISION Z
COMMON /WIM/ Z(2)
]
> But, the argument is dimensioned by a component of a common area -- more
> to the point, a *local* mapping of that common area. (I.e. there is,
> in Fortran, no "toplevel" mapping of a common area that everyone agrees
> to -- there's just the rough equivalent of "[extern] char commonarea[SIZE];".
> Each toplevel procedure gets to decide whether, say, the third word
> in it is an integer named N, a float named V, or whatever.)
Yech - this is the first time that I actually understand the difficulty
in supporting debug info for COMMON (and the reason to treat COMMON as a
char array instead of a structure).
Bah - no wonder this is so hard ...
Thanks for the explanation, Craig !
--
Toon Moene (toon@moene.indiv.nluug.nl)
Saturnushof 14, 3738 XG Maartensdijk, The Netherlands
Phone: +31 346 214290; Fax: +31 346 214286
GNU Fortran: http://world.std.com/~burley/g77.html