gdb: Fix failure in gdb.base/complex-parts.exp for x86-32
authorAndrew Burgess <andrew.burgess@embecosm.com>
Fri, 12 Apr 2019 23:54:16 +0000 (00:54 +0100)
committerAndrew Burgess <andrew.burgess@embecosm.com>
Sat, 13 Apr 2019 00:02:43 +0000 (01:02 +0100)
commit35add35e85c21f02e3e5808273cb77b24069b0aa
tree169eb966bc2076dd5e00011fbd58c0129441d2b0
parent9c9f1b1f39f37ce75c2fc3c378aa059b67df2ea2
gdb: Fix failure in gdb.base/complex-parts.exp for x86-32

The x86-32 ABI specifies 96-bit long double, this was causing a
failure on the test gdb.base/complex-parts.exp.

The problem is that GDB tries to find a builtin floating point type of
the correct size in order to reuse the name of that type as the name
for the components of the complex type being built.

Previously GDB was only aware of floating point types sized 32, 64, or
128 bits.  This patch teaches GDB how to handle 96 bit floating point
type.

gdb/ChangeLog:

* dwarf2read.c (dwarf2_init_complex_target_type): Handle complex
target types of size 96-bits, add some additional comments, and
check that the builtin type we found was the correct size.
gdb/ChangeLog
gdb/dwarf2read.c