diff options
author | Tom Tromey <tromey@adacore.com> | 2023-11-22 06:54:40 -0700 |
---|---|---|
committer | Tom Tromey <tom@tromey.com> | 2023-11-22 21:20:37 -0700 |
commit | a54a99a6e5159e4406e172f074b3729b2135c28c (patch) | |
tree | 6b452fc57b84efd0370dbfc71bb3b7906aef0e70 /gdb/testsuite/gdb.python/py-completion.py | |
parent | d95ba7227e2185ed83e5d62975f2ca76f445146c (diff) | |
download | binutils-a54a99a6e5159e4406e172f074b3729b2135c28c.zip binutils-a54a99a6e5159e4406e172f074b3729b2135c28c.tar.gz binutils-a54a99a6e5159e4406e172f074b3729b2135c28c.tar.bz2 |
Fix build with GCC 7.5
A recent change to 'struct field' caused a build failure with GCC
7.5.0, as reported by Tom de Vries:
/data/vries/gdb/src/gdb/gdbtypes.h:721:51: error:
‘field::m_accessibility’ is too small to hold all values of ‘enum
class accessibility’ [-Werror]
ENUM_BITFIELD (accessibility) m_accessibility : 2;
^
Mark Wielaard pointed out that this was a GCC bug:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51242
This patch works around the bug by changing several members not to be
bitfields. It reduces the size of the enum's underlying type,
instead.
I also changed m_bitsize to no longer be a bitfield -- that was done
for packing reasons in ancient times, but with m_accessibility not
being a bitfield, this no longer matters.
I removed fn_field::dummy. In earlier times it was somewhat normal in
gdb to have these dummy fields to keep track of any available padding.
However, since the advent of "ptype/o", there doesn't seem to be any
need for this.
This patch does not change the size of struct field, fn_field, or
decl_field on 64-bit hosts.
Diffstat (limited to 'gdb/testsuite/gdb.python/py-completion.py')
0 files changed, 0 insertions, 0 deletions