aboutsummaryrefslogtreecommitdiff
path: root/gdb/objfiles.c
diff options
context:
space:
mode:
authorAndrew Burgess <andrew.burgess@embecosm.com>2019-02-16 22:45:41 +0000
committerAndrew Burgess <andrew.burgess@embecosm.com>2019-04-30 10:10:31 +0100
commit1db455a76c39e2be6a8a9613b7a19439f24722d0 (patch)
tree80df9448123cfcc3c159f5e209c2ba94ddd805cc /gdb/objfiles.c
parentb6d03bb2b65ac5c919f1d08674bbaa2a9bfb2d0c (diff)
downloadbinutils-1db455a76c39e2be6a8a9613b7a19439f24722d0.zip
binutils-1db455a76c39e2be6a8a9613b7a19439f24722d0.tar.gz
binutils-1db455a76c39e2be6a8a9613b7a19439f24722d0.tar.bz2
gdb/fortran: better types for components of complex numbers
Currently when using $_creal and $_cimag to access the components of a complex number the types of these components will have C type names 'float', 'double', etc. This is because the components of a complex number are not given type names in DWARF, so GDB has to pick some suitable names, and currently we always use the C names. This commit changes the type names used based on the language, so for Fortran we will now use the Fortran float types, and so will get the Fortran float type names 'real', 'real*8', etc. gdb/ChangeLog: * dwarf2read.c (dwarf2_init_complex_target_type): Use different types for Fortran. gdb/testsuite/ChangeLog: * gdb.fortran/complex.exp: Expand. * gdb.fortran/complex.f: Renamed to... * gdb.fortran/complex.f90: ...this, and extended to add more complex values.
Diffstat (limited to 'gdb/objfiles.c')
0 files changed, 0 insertions, 0 deletions