aboutsummaryrefslogtreecommitdiff
path: root/gcc/function.cc
diff options
context:
space:
mode:
authorPatrick Palka <ppalka@redhat.com>2022-02-10 08:54:07 -0500
committerPatrick Palka <ppalka@redhat.com>2022-02-10 08:54:07 -0500
commit3d7341cd731247c2ff6709a000837a6c924247f3 (patch)
tree8aacb1c758fb742403cf06c8975cc649bbb2833e /gcc/function.cc
parent3881e1823c5a59d988ddcddcc1e25c5738e228fb (diff)
downloadgcc-3d7341cd731247c2ff6709a000837a6c924247f3.zip
gcc-3d7341cd731247c2ff6709a000837a6c924247f3.tar.gz
gcc-3d7341cd731247c2ff6709a000837a6c924247f3.tar.bz2
c++: memfn lookup consistency and dependent using-decls
Rather than not doing any filtering when filter_memfn_lookup encounters a dependent using-decl, handle this case less imprecisely by holding on to the members in the new lookup set that come from a base, i.e. that could plausibly have been introduced by that using-decl, and filtering the rest as usual. This is still imperfect, but it's closer to the correct answer than the previous behavior was. gcc/cp/ChangeLog: * pt.cc (filter_memfn_lookup): Handle dependent USING_DECL better.
Diffstat (limited to 'gcc/function.cc')
0 files changed, 0 insertions, 0 deletions