public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Jim Wilson <wilson@redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: debug/1621: Debugging with complex numbers Date: Thu, 12 Dec 2002 13:36:00 -0000 [thread overview] Message-ID: <20021212213601.11960.qmail@sources.redhat.com> (raw) 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
next reply other threads:[~2002-12-12 21:36 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-12 13:36 Jim Wilson [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-12-28 10:59 jsm28 2002-12-13 11:26 Joseph S. Myers 2002-12-13 9:32 wilson 2002-12-12 14:16 Jim Wilson 2002-12-12 11:56 Daniel Jacobowitz 2002-12-12 7:56 Jim Wilson 2002-12-11 17:26 Daniel Jacobowitz 2002-12-11 16:16 Jim Wilson 2002-12-09 12:24 bangerth 2002-12-07 17:26 Daniel Jacobowitz 2002-12-05 16:16 Wolfgang Bangerth 2002-12-05 15:26 Joseph S. Myers 2002-12-05 12:09 bangerth 2001-04-01 0:00 Joseph Myers
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20021212213601.11960.qmail@sources.redhat.com \ --to=wilson@redhat.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).