aboutsummaryrefslogtreecommitdiff
path: root/bfd/elf32-microblaze.c
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2020-07-30 12:35:57 +0200
committerTom de Vries <tdevries@suse.de>2020-07-30 12:35:57 +0200
commit6cc64caabac2f835149d0931d5ab689ccca1ca08 (patch)
tree101c588990e6161319c7c0b595563d2154bbf3f6 /bfd/elf32-microblaze.c
parent4d8ee860737005517be588f4771c358593fa421c (diff)
downloadbinutils-6cc64caabac2f835149d0931d5ab689ccca1ca08.zip
binutils-6cc64caabac2f835149d0931d5ab689ccca1ca08.tar.gz
binutils-6cc64caabac2f835149d0931d5ab689ccca1ca08.tar.bz2
[gdb/testsuite] Fix gdb.fortran/ptype-on-functions.exp with gcc-4.8
When running test-case gdb.fortran/ptype-on-functions.exp with gfortran 4.8.5, we run into: ... (gdb) ptype some_module::get_number^M type = integer(kind=4) (Type __class_some_module_Number)^M (gdb) FAIL: gdb.fortran/ptype-on-functions.exp: ptype some_module::get_number ptype some_module::set_number^M type = void (Type __class_some_module_Number, integer(kind=4))^M (gdb) FAIL: gdb.fortran/ptype-on-functions.exp: ptype some_module::set_number ... The test-case pattern expects a "_t" suffix on "__class_some_module_Number". The difference is caused by a gcc commit 073afca6884 'class.c (gfc_build_class_symbol): Append "_t" to target class names to make the generated type names unique' which has been present since gcc 4.9.0. Fix the pattern by optionally matching the _t suffix. Tested on x86_64-linux, with gfortran 4.8.5 and 7.5.0. gdb/testsuite/ChangeLog: 2020-07-30 Tom de Vries <tdevries@suse.de> * gdb.fortran/ptype-on-functions.exp: Make "_t" suffix on "__class_some_module_Number_t" optional.
Diffstat (limited to 'bfd/elf32-microblaze.c')
0 files changed, 0 insertions, 0 deletions