Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: George Helffrich +44 117 954 5437 <george@geology.bristol.ac.uk>
To: drow@mvista.com, gcc-bugs@gcc.gnu.org, gdb@sources.redhat.com,
	law@redhat.com
Subject: Re:  Debug info for 'complex' types
Date: Fri, 01 Feb 2002 02:34:00 -0000	[thread overview]
Message-ID: <200202011034.g11AYO002233@olivine.geology.bristol.ac.uk> (raw)

I proposed this change also to fix complex value support in GDB (I use
g77, gdb and complex arithmetic extensively in my line of work).  My base
version was GDB 4.16.  (I can send you patches if you are interested.)  After
studying all stabs documentation I could find (with no particular illumination
on the issue of complex types), I also compared stabs output from other
Fortran compilers available to me.  Here they are:

From Solaris 2.7 SC4.2 f77:

	.stabs  "complex*8:t9=R3;8",32,0,0,0

From SunOS 4.1.3 f77:

	.stabs  "complex:t7=r7;8;0;",0x20,0,0,0

and with the patch I proposed for g77 (2.95.2 19991024 release, patched):

.stabs "complex float:t(0,16)=r(0,16);8;0;",128,0,0,0

I think this indicates the length should be 8 for a single precision complex
value.  If you want gdb to even think about supporting Sun Fortran compiler
stabs (my gdb tries to do so), *don't* withdraw this patch.  Tell your users
to recompile if they want to debug code with complex arithmetic.

                                       George Helffrich
                                       (george@geology.bristol.ac.uk)


             reply	other threads:[~2002-02-01 10:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-01  2:34 George Helffrich +44 117 954 5437 [this message]
2002-02-01  7:26 ` Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2002-02-01  7:53 George Helffrich +44 117 954 5437
2002-02-01  8:39 ` Andrew Cagney
2002-02-01  9:06   ` Daniel Jacobowitz
2002-01-30 20:26 Daniel Jacobowitz

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=200202011034.g11AYO002233@olivine.geology.bristol.ac.uk \
    --to=george@geology.bristol.ac.uk \
    --cc=drow@mvista.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=law@redhat.com \
    /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: link
Be 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