Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org, Pierre Muller <muller@ics.u-strasbg.fr>
Subject: Is bitstring support still useful?
Date: Fri, 17 Jul 2009 14:33:00 -0000	[thread overview]
Message-ID: <20090717143315.GA29728@caradoc.them.org> (raw)

GDB contains both type (TYPE_CODE_BITSTRING) and expression
(OP_BITSTRING) support for bitstrings.  This is in the way for some
bitfield changes I'd like to make, and before I spend time fixing it,
I'd like to know if it's still useful.

OP_BITSTRING is currently dead code.  It's handled in a number of
places, but never generated.

TYPE_CODE_BITSTRING can be generated two ways: from OP_BITSTRING (so,
dead) or from the stabs reader.  It's not generated from any other
symbol reader, including DWARF.  Does this mean it's dead or that
there's something the DWARF reader should do?

For now, I'm going to remove support in my local tree.

Pierre, I've copied you because the most recent non-mechanical patch
related to bitstrings was yours, a long while ago:

2002-05-02  Pierre Muller  <muller@ics.u-strasbg.fr>

        * p-typeprint.c (pascal_type_print_base): Add support
        for TYPE_CODE_STRING and TYPE_CODE_BITSTRING.

(I'm not sure you'll receive my mail directly, though - something
about the IPv6 addresses used by u-strasbg.fr causes my mail server a
lot of grief.)

-- 
Daniel Jacobowitz
CodeSourcery


             reply	other threads:[~2009-07-17 14:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-17 14:33 Daniel Jacobowitz [this message]
2009-07-17 14:41 ` Daniel Jacobowitz
2009-07-17 15:01   ` Jonas Maebe
2009-07-18  4:09     ` Daniel Jacobowitz
2009-07-18 15:17       ` Jonas Maebe

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=20090717143315.GA29728@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=muller@ics.u-strasbg.fr \
    /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