| commit | ecbc5c4f9059dd483cf8b0705cbd4e2e9606aad5 | |
| author | Felix Willgerodt <felix.willgerodt@intel.com> | |
| Mon, 13 Feb 2023 10:02:23 +0000 (13 11:02 +0100) | ||
| committer | Felix Willgerodt <felix.willgerodt@intel.com> | |
| Wed, 15 Feb 2023 08:51:28 +0000 (15 09:51 +0100) | ||
| tree | 43827ec45e63690388b13e05cf33cfa74bddcf66 | treesnapshot (tar.gz zip) |
| parent | c22a74728313ee35f6bf143238d42e2eca9ed020 | commitdiff |
gdb, fortran: Fix quad floating-point type for ifort compiler.
I fixed this a while ago for ifx, one of the two Intel compilers, in
8d624a9d8050ca96e154215c7858ac5c2d8b0b19.
Apparently I missed that the older ifort Intel compiler actually emits
slightly different debug info again:
0x0000007a: DW_TAG_base_type
DW_AT_byte_size (0x20)
DW_AT_encoding (DW_ATE_complex_float)
DW_AT_name ("COMPLEX(16)")
0x00000081: DW_TAG_base_type
DW_AT_byte_size (0x10)
DW_AT_encoding (DW_ATE_float)
DW_AT_name ("REAL(16)")
This fixes two failures in gdb.fortran/complex.exp with ifort.
Approved-By: Tom Tromey <tom@tromey.com>
I fixed this a while ago for ifx, one of the two Intel compilers, in
8d624a9d8050ca96e154215c7858ac5c2d8b0b19.
Apparently I missed that the older ifort Intel compiler actually emits
slightly different debug info again:
0x0000007a: DW_TAG_base_type
DW_AT_byte_size (0x20)
DW_AT_encoding (DW_ATE_complex_float)
DW_AT_name ("COMPLEX(16)")
0x00000081: DW_TAG_base_type
DW_AT_byte_size (0x10)
DW_AT_encoding (DW_ATE_float)
DW_AT_name ("REAL(16)")
This fixes two failures in gdb.fortran/complex.exp with ifort.
Approved-By: Tom Tromey <tom@tromey.com>
| gdb/i386-tdep.c | diffblobblamehistory |