Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jonas Maebe <jonas.maebe@elis.ugent.be>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sourceware.org,  Pierre Muller <muller@ics.u-strasbg.fr>
Subject: Re: Is bitstring support still useful?
Date: Sat, 18 Jul 2009 15:17:00 -0000	[thread overview]
Message-ID: <606C7EEE-E4B3-4C23-A4D3-94D6DE6E4A6E@elis.ugent.be> (raw)
In-Reply-To: <20090718040915.GA15792@caradoc.them.org>


On 18 Jul 2009, at 06:09, Daniel Jacobowitz wrote:

> Does this compiler support DWARF,

Yes.

> and if so, how do you represent them
> there?

type
   ta = bitpacked array[1..10] of 0..2;

becomes:

0x0000007d:     TAG_array_type [5] *
                  AT_name( "TA" )
                  AT_byte_size( 0x00000003 )
                  AT_bit_stride( 0x00000002 )
                  AT_type( {0x00000094} ( subrange BYTE ) )

0x00000087:         TAG_subrange_type [6]
                      AT_lower_bound( 0x00000001 )
                      AT_upper_bound( 0x0000000a )
                      AT_type( {0x000000a0} ( SHORTINT ) )

0x0000008e:         NULL


gdb does not handle this yet though (DW_AT_bit_stride is unsupported  
in dwarf2read.c). Printing a variable of this type therefore prints it  
as if it were an array of 10 bytes. But at least the concept is  
representable in DWARF-3, and it just needs fixes in the DWARF reader  
(and possibly in the Pascal printer).


Jonas


      reply	other threads:[~2009-07-18 15:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-17 14:33 Daniel Jacobowitz
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 [this message]

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=606C7EEE-E4B3-4C23-A4D3-94D6DE6E4A6E@elis.ugent.be \
    --to=jonas.maebe@elis.ugent.be \
    --cc=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