aboutsummaryrefslogtreecommitdiff
path: root/gcc/gcov-tool.cc
diff options
context:
space:
mode:
authorBernhard Reutner-Fischer <aldot@gcc.gnu.org>2023-06-01 19:44:19 +0200
committerBernhard Reutner-Fischer <aldot@gcc.gnu.org>2023-11-15 18:38:45 +0100
commit186331063dfbcf1eacb445c473d92634c9baa90f (patch)
treee6cf8e7ad41ffc7f9f4629e239f723deb36a9520 /gcc/gcov-tool.cc
parentd1189ceefc1da1515e039c9cfd2f5a67b5820207 (diff)
downloadgcc-186331063dfbcf1eacb445c473d92634c9baa90f.zip
gcc-186331063dfbcf1eacb445c473d92634c9baa90f.tar.gz
gcc-186331063dfbcf1eacb445c473d92634c9baa90f.tar.bz2
c++, analyzer: Expand CAN_HAVE_LOCATION_P macro.
r14-985-gca2007a9bb3074 used the collapsed macro definition CAN_HAVE_LOCATION_P in gcc-rich-location.cc and r14-977-g8861c80733da5c in c++'s build_cplus_array_type (). However, although otherwise correct, the usage of CAN_HAVE_LOCATION_P in these two spots is misleading, so this patch reverts aforementioned two hunks. gcc/cp/ChangeLog: * tree.cc (build_cplus_array_type): Revert using the macro CAN_HAVE_LOCATION_P. gcc/ChangeLog: * gcc-rich-location.cc (maybe_range_label_for_tree_type_mismatch::get_text): Revert using the macro CAN_HAVE_LOCATION_P.
Diffstat (limited to 'gcc/gcov-tool.cc')
0 files changed, 0 insertions, 0 deletions