https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116320
--- Comment #4 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-14 branch has been updated by Patrick Palka <ppa...@gcc.gnu.org>: https://gcc.gnu.org/g:149d87fbe661da29d8a0aa671b42bd532206a8b8 commit r14-10656-g149d87fbe661da29d8a0aa671b42bd532206a8b8 Author: Patrick Palka <ppa...@redhat.com> Date: Thu Aug 15 10:23:54 2024 -0400 c++: c->B::m access resolved through current inst [PR116320] Here when checking the access of (the injected-class-name) B in c->B::m at parse time, we notice its context B (now the type) is a base of the object type C<T>, so we proceed to use C<T> as the effective qualifying type. But this C<T> is the dependent specialization not the primary template type, so it has empty TYPE_BINFO, which leads to a segfault later from perform_or_defer_access_check. The reason the DERIVED_FROM_P (B, C<T>) test guarding this code path works despite C<T> having empty TYPE_BINFO is because of its currently_open_class logic (added in r9-713-gd9338471b91bbe) which replaces a dependent specialization with the primary template type if we're inside it. So the safest fix seems to be to call currently_open_class in the caller as well. PR c++/116320 gcc/cp/ChangeLog: * semantics.cc (check_accessibility_of_qualified_id): Try currently_open_class when using the object type as the effective qualifying type. gcc/testsuite/ChangeLog: * g++.dg/template/access42.C: New test. Reviewed-by: Jason Merrill <ja...@redhat.com> (cherry picked from commit 484f139ccd3b631a777802e810a632678b42ffab)
