diff options
| author | Doug Evans <dje@google.com> | 2016-10-06 12:12:33 +0100 |
|---|---|---|
| committer | Pedro Alves <palves@redhat.com> | 2016-10-06 12:12:33 +0100 |
| commit | ee8da4b8396d9a74d27cb9bb0f3aa43d6d23b8ea (patch) | |
| tree | 1fd455f93881201680ad490eb1e54d62647b33d6 /gdb/doc/gdb.texinfo | |
| parent | 3ac6b810d1e58fe10ee496fdb1ebd4ce050dc91c (diff) | |
| download | gdb-ee8da4b8396d9a74d27cb9bb0f3aa43d6d23b8ea.zip gdb-ee8da4b8396d9a74d27cb9bb0f3aa43d6d23b8ea.tar.gz gdb-ee8da4b8396d9a74d27cb9bb0f3aa43d6d23b8ea.tar.bz2 | |
Make "end" field in feature specs required again.
Newer gdbservers may be talking to older gdbs,
and older gdbs will flag a missing "end" as an error.
So just make "end" required again, and for compatibility
change the default field type to "bool".
gdb/ChangeLog:
2016-10-06 Doug Evans <dje@google.com>
* features/aarch64-core.xml (cpsr_flags): Elide "type" and specify
"end" in all fields.
* features/aarch64.c: Regenerate.
* features/i386/32bit-mpx.xml (_bndcfgu): Specify type of "preserved"
and "enabled" fields. Correct size of "enabled" field.
* features/i386/64bit-mpx.xml (_bndcfgu): Specify type of "preserved"
and "enabled" fields.
* features/i386/i386-avx-mpx-linux.c: Regenerate.
* features/i386/i386-avx-mpx.c: Regenerate.
* features/i386/i386-avx512-linux.c: Regenerate.
* features/i386/i386-avx512.c: Regenerate.
* features/i386/i386-mpx-linux.c: Regenerate.
* features/i386/i386-mpx.c: Regenerate.
* features/arc-arcompact.c: Regenerate.
* features/arc-v2.c: Regenerate.
* xml-tdesc.c (tdesc_start_field): Require "end" spec. Single bit
fields default to "bool" type.
Revert 2016-03-15 Doug Evans <dje@google.com>
* features/i386/32bit-core.xml (i386_eflags): Remove "end" spec.
* features/i386/32bit-sse.xml (i386_eflags): Ditto.
* features/i386/64bit-core.xml (i386_eflags): Ditto.
* features/i386/64bit-sse.xml (i386_eflags): Ditto.
* features/i386/x32-core.xml (i386_eflags): Ditto.
gdb/doc/ChangeLog:
2016-10-06 Doug Evans <dje@google.com>
* gdb.texinfo (Target Description Format): Update docs on "end"
field spec and field default type.
gdb/testsuite/ChangeLog:
2016-10-06 Doug Evans <dje@google.com>
* gdb.xml/extra-regs.xml: Update, end field now required, default type
for single bitfields is bool.
* gdb.xml/tdesc-regs.exp: Ditto.
Diffstat (limited to 'gdb/doc/gdb.texinfo')
| -rw-r--r-- | gdb/doc/gdb.texinfo | 11 |
1 files changed, 4 insertions, 7 deletions
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 344c186..cfa00ce 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -40722,16 +40722,13 @@ Bitfield values may be named with the empty string, @samp{""}, in which case the field is ``filler'' and its value is not printed. Not all bits need to be specified, so ``filler'' fields are optional. -The @var{start} value is required, and @var{end} and @var{type} -are optional. +The @var{start} and @var{end} values are required, and @var{type} +is optional. The field's @var{start} must be less than or equal to its @var{end}, and zero represents the least significant bit. -The default value of @var{end} is @var{start}, a single bit field. -The default value of @var{type} depends on whether the -@var{end} was specified. If @var{end} is specified then the default -value of @var{type} is an unsigned integer. If @var{end} is unspecified -then the default value of @var{type} is @code{bool}. +The default value of @var{type} is @code{bool} for single bit fields, +and an unsigned integer otherwise. Which to choose? Structures or flags? |