On Feb 7, 2019, Jason Merrill <ja...@redhat.com> wrote: > In protected_accessible_p and shared_member_p, if we're left with a > USING_DECL after strip_using_decl, we can't give a meaningful answer, > and should probably abort; we shouldn't get here with a dependent > expression.
In g++.dg/lookup/using39.C, shared_member_p is called by cp_parser_primary_expression -> finish_id_expression -> finish_id_expression_1 -> finish_qualified_id_expr when parsing 'using A<T>::f' in B<T>. That was the only regression in the patch I posted earlier today. I'm going back to the previous version of shared_member_p. -- Alexandre Oliva, freedom fighter https://FSFLA.org/blogs/lxo Be the change, be Free! FSF Latin America board member GNU Toolchain Engineer Free Software Evangelist Hay que enGNUrecerse, pero sin perder la terGNUra jamás-GNUChe
