debug/1621: Debugging with complex numbers

[Jim Wilson]

The following reply was made to PR debug/1621; it has been noted by GNATS.

From: Jim Wilson <wilson@redhat.com>
To: "Joseph S. Myers" <jsm28@cam.ac.uk>
Cc: Wolfgang Bangerth <bangerth@ticam.utexas.edu>,
   Daniel Jacobowitz <drow@mvista.com>, bangerth@dealii.org,
   gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: debug/1621: Debugging with complex numbers
Date: 12 Dec 2002 16:30:10 -0500

 Here is an attempt to fix the documentation problem.  Comments?
 
 2002-12-12  Jim Wilson  <wilson@redhat.com>
 
 	* doc/extend.texi (Complex Numbers): Update info on debug info.
 
 Index: extend.texi
 ===================================================================
 RCS file: /cvs/gcc/gcc/gcc/doc/extend.texi,v
 retrieving revision 1.108
 diff -p -r1.108 extend.texi
 *** extend.texi	27 Nov 2002 06:32:13 -0000	1.108
 --- extend.texi	12 Dec 2002 20:46:44 -0000
 *************** provided as built-in functions by GCC@.
 *** 1224,1239 ****
   
   GCC can allocate complex automatic variables in a noncontiguous
   fashion; it's even possible for the real part to be in a register while
 ! the imaginary part is on the stack (or vice-versa).  None of the
 ! supported debugging info formats has a way to represent noncontiguous
 ! allocation like this, so GCC describes a noncontiguous complex
 ! variable as if it were two separate variables of noncomplex type.
   If the variable's actual name is @code{foo}, the two fictitious
   variables are named @code{foo$real} and @code{foo$imag}.  You can
   examine and set these two fictitious variables with your debugger.
 - 
 - A future version of GDB will know how to recognize such pairs and treat
 - them as a single variable with a complex type.
   
   @node Hex Floats
   @section Hex Floats
 --- 1224,1236 ----
   
   GCC can allocate complex automatic variables in a noncontiguous
   fashion; it's even possible for the real part to be in a register while
 ! the imaginary part is on the stack (or vice-versa).  Only the DWARF2
 ! debug info format can represent this, so use of DWARF2 is recommended.
 ! If you are using the stabs debug info format, GCC describes a noncontiguous
 ! complex variable as if it were two separate variables of noncomplex type.
   If the variable's actual name is @code{foo}, the two fictitious
   variables are named @code{foo$real} and @code{foo$imag}.  You can
   examine and set these two fictitious variables with your debugger.
   
   @node Hex Floats
   @section Hex Floats