diff options
| author | Carl Love <cel@us.ibm.com> | 2023-03-23 18:23:05 -0400 |
|---|---|---|
| committer | Carl Love <cel@us.ibm.com> | 2023-04-18 11:03:08 -0400 |
| commit | c1a398a320f46905eaf6f520dddc441791861dcb (patch) | |
| tree | cc83eb566cd1183ca7e6d94c6a755d997a2987a4 /gdb/gdbarch-gen.h | |
| parent | a02676b77d84d8229b5d4b01259535234cded19e (diff) | |
| download | binutils-c1a398a320f46905eaf6f520dddc441791861dcb.zip binutils-c1a398a320f46905eaf6f520dddc441791861dcb.tar.gz binutils-c1a398a320f46905eaf6f520dddc441791861dcb.tar.bz2 | |
PowerPC: fix _Float128 type output string
PowerPC supports two 128-bit floating point formats, the IBM long double
and IEEE 128-bit float. The issue is the DWARF information does not
distinguish between the two. There have been proposals of how to extend
the DWARF information as discussed in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104194
but has not been fully implemented.
GCC introduced the _Float128 internal type as a work around for the issue.
The workaround is not transparent to GDB. The internal _Float128 type
name is printed rather then the user specified long double type. This
patch adds a new gdbarch method to allow PowerPC to detect the GCC
workaround. The workaround checks for "_Float128" name when reading the
base typedef from the die_info. If the workaround is detected, the type
and format fields from the _Float128 typedef are copied to the long
double typedef. The same is done for the complex long double typedef.
This patch fixes 74 regression test failures in
gdb.base/whatis-ptype-typedefs.exp on PowerPC with IEEE float 128 as the
default on GCC. It fixes one regression test failure in
gdb.base/complex-parts.exp.
The patch has been tested on Power 10 where GCC defaults to IEEE Float
128-bit and on Power 10 where GCC defaults to the IBM 128-bit float. The
patch as also been tested on X86-64 with no new regression failures.
Diffstat (limited to 'gdb/gdbarch-gen.h')
| -rw-r--r-- | gdb/gdbarch-gen.h | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/gdb/gdbarch-gen.h b/gdb/gdbarch-gen.h index a2bd08b..56b0a91 100644 --- a/gdb/gdbarch-gen.h +++ b/gdb/gdbarch-gen.h @@ -468,6 +468,14 @@ typedef CORE_ADDR (gdbarch_get_return_buf_addr_ftype) (struct type *val_type, fr extern CORE_ADDR gdbarch_get_return_buf_addr (struct gdbarch *gdbarch, struct type *val_type, frame_info_ptr cur_frame); extern void set_gdbarch_get_return_buf_addr (struct gdbarch *gdbarch, gdbarch_get_return_buf_addr_ftype *get_return_buf_addr); +/* Return true if the typedef record needs to be replaced.". + + Return 0 by default */ + +typedef bool (gdbarch_dwarf2_omit_typedef_p_ftype) (struct type *target_type, const char *producer, const char *name); +extern bool gdbarch_dwarf2_omit_typedef_p (struct gdbarch *gdbarch, struct type *target_type, const char *producer, const char *name); +extern void set_gdbarch_dwarf2_omit_typedef_p (struct gdbarch *gdbarch, gdbarch_dwarf2_omit_typedef_p_ftype *dwarf2_omit_typedef_p); + /* Return true if the return value of function is stored in the first hidden parameter. In theory, this feature should be language-dependent, specified by language and its ABI, such as C++. Unfortunately, compiler may |