Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Jeffrey Law <law@redhat.com>,
	George Helffrich <george@gly.bris.ac.uk>,
	gcc-bugs@gcc.gnu.org
Cc: gdb@sources.redhat.com
Subject: Debug info for 'complex' types
Date: Wed, 30 Jan 2002 20:26:00 -0000	[thread overview]
Message-ID: <20020130232558.A21136@nevyn.them.org> (raw)

While otherwise fixing complex value support in GDB, I came across this
patch:

Sun Jul 23 11:52:03 2000  George Helffrich (george@gly.bris.ac.uk)

        * dbxout.c (dbxout_type, case COMPLEX_TYPE): Fix length field in stab.

It's wrong - the GDB stabs reader says:
  /* If n3 is zero and n2 is positive, we want a floating type, and n2
     is the width in bytes.

     Fortran programs appear to use this for complex types also.  To
     distinguish between floats and complex, g77 (and others?)  seem
     to use self-subranges for the complexes, and subranges of int for
     the floats.

     Also note that for complexes, g77 sets n2 to the size of one of
     the member floats, not the whole complex beast.  My guess is that
     this was to work well with pre-COMPLEX versions of gdb. */

This was true as late as 2.95.3, and broken by this patch.  Can it be
reverted for 3.0.4 and 3.1, please?  There's no way for GDB to tell if this
change is present or not in any reasonable fashion, so there is no way to
support it.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


             reply	other threads:[~2002-01-31  4:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-30 20:26 Daniel Jacobowitz [this message]
2002-02-01  2:34 George Helffrich +44 117 954 5437
2002-02-01  7:26 ` Daniel Jacobowitz
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

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=20020130232558.A21136@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=george@gly.bris.ac.uk \
    --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