diff options
| author | Nils-Christian Kempke <nils-christian.kempke@intel.com> | 2022-01-17 12:30:05 +0100 |
|---|---|---|
| committer | Tom Tromey <tromey@adacore.com> | 2022-01-31 10:14:47 -0700 |
| commit | 8d2ef06e1c220bcfb133a47b98b6287ccabdb587 (patch) | |
| tree | e139d8d991ca2116f81877a14edd267d68d34267 /gdb/disasm.c | |
| parent | f10f8617a302f45dae721eae0cd659911f03d864 (diff) | |
| download | gdb-8d2ef06e1c220bcfb133a47b98b6287ccabdb587.zip gdb-8d2ef06e1c220bcfb133a47b98b6287ccabdb587.tar.gz gdb-8d2ef06e1c220bcfb133a47b98b6287ccabdb587.tar.bz2 | |
gdb, testsuite, fortran: adapt info symbol expected output for intel compilers
Info symbol is expected to print the symbol table name of a symbol, since
symbol lookup happens via the minimal symbol table. This name
corresponds to the linkage name in the full symbol table.
For gfortran (and maybe others) these names currently have the form
XXXX.NUMBER where XXXX is the symbol name and NUMBER a compiler
generated appendix for mangling.
An example taken from the modified nested-funcs-2.exp would be
~~~~
$ objdump -t ./outputs/gdb.fortran/nested-funcs-2/nested-funcs-2 | grep \
increment
00000000000014ab l F .text 0000000000000095 increment.3883
000000000000141c l F .text 000000000000008f increment_program_global.3881
~~~~
This mangled name gets recognized by the Ada demangler/decoder and decoded as
Ada to XXXX (setting the symbol language to Ada). This leads to output
of XXXX over XXXX.NUMBER for info symbol on gfortran symbols.
For ifort and ifx the generated linkage names have the form
SCOPEA_SCOPEB_XXXX_ which are not recognized by the Ada decoder (or any
other demangler for that matter) and thus printed as is.
The respective objdump in the above case looks like
~~~~
$ objdump -t ./outputs/gdb.fortran/nested-funcs-2/nested-funcs-2 | grep \
increment
0000000000403a44 l F .text 0000000000000074 contains_keyword_IP_increment_
0000000000403ab8 l F .text 0000000000000070
contains_keyword_IP_increment_program_global_
~~~~
In the unmodified testcase this results in 'fails' when ran with the intel
compilers:
~~~~
>> make check RUNTESTFLAGS="gdb.fortran/nested-funcs-2.exp \
GDBFLAGS='$GDBFLAGS' CC_FOR_TARGET='icpc' F90_FOR_TARGET='ifort'"
...
=== gdb Summary ===
\# of expected passes 80
\# of unexpected failures 14
~~~~
Note that there is no Fortran mangling standard. We keep the gfortran
behavior as is and modify the test to reflect ifx and ifort mangled
names which fixes above fails.
Signed-off-by: Nils-Christian Kempke <nils-christian.kempke@intel.com>
Diffstat (limited to 'gdb/disasm.c')
0 files changed, 0 insertions, 0 deletions