From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/doco] Fix gdb.Field attributes documentation for enum types.
Date: Sat, 28 Dec 2013 09:05:00 -0000 [thread overview]
Message-ID: <83vby92vo5.fsf@gnu.org> (raw)
In-Reply-To: <20131228033003.GD4532@adacore.com>
> Date: Sat, 28 Dec 2013 07:30:03 +0400
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
>
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -24338,8 +24338,8 @@ Each field is a @code{gdb.Field} object, with some pre-defined attributes:
> @table @code
> @item bitpos
> This attribute is not available for @code{enum} or @code{static}
> -(as in C@t{++} or Java) fields. The value is the bit position of
> -the field.
> +(as in C@t{++} or Java) fields. The value is the position, counting
> +in bits, from the start of the containing type.
Thanks, this is clear.
I'm curious: why are the bit units useful? Field offsets are
generally counted in bytes, not bits.
next prev parent reply other threads:[~2013-12-28 9:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 7:23 Joel Brobecker
2013-12-23 16:15 ` Eli Zaretskii
2013-12-28 3:30 ` Joel Brobecker
2013-12-28 9:05 ` Eli Zaretskii [this message]
2013-12-30 2:57 ` Joel Brobecker
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=83vby92vo5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.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: 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