diff options
author | Tom Tromey <tromey@adacore.com> | 2024-08-21 11:46:52 -0600 |
---|---|---|
committer | Tom Tromey <tromey@adacore.com> | 2025-04-01 10:41:34 -0600 |
commit | 2fd74c790556a3de6c42efa564781aa2ac0e3596 (patch) | |
tree | c7b54d78680b99f18536dc2342982b7bef835b86 /gcc/fortran/interface.cc | |
parent | 01acd453d89ff5e414fade2dfeeae1f652143376 (diff) | |
download | gcc-2fd74c790556a3de6c42efa564781aa2ac0e3596.zip gcc-2fd74c790556a3de6c42efa564781aa2ac0e3596.tar.gz gcc-2fd74c790556a3de6c42efa564781aa2ac0e3596.tar.bz2 |
Further use of mod_scope in modified_type_die
I am working on some changes to GNAT to emit hierarchical DWARF --
i.e., where entities will have simple names nested in a DW_TAG_module.
While working on this I found a couple of paths in modified_type_die
where "mod_scope" should be used, but is not. I suspect these cases
are only reachable by Ada code, as in both spots (subrange types and
base types), I believe that other languages don't generally have named
types in a non-top-level scope, and in these other situations,
mod_scope will still be correct.
gcc
* dwarf2out.cc (modified_type_die): Use mod_scope for
ranged types, base types, and array types.
Diffstat (limited to 'gcc/fortran/interface.cc')
0 files changed, 0 insertions, 0 deletions