aboutsummaryrefslogtreecommitdiff
path: root/gcc/value-range.cc
diff options
context:
space:
mode:
authorPatrick Palka <ppalka@redhat.com>2022-09-17 09:16:53 -0400
committerPatrick Palka <ppalka@redhat.com>2022-09-17 09:16:53 -0400
commitf4dad09c543eebc4d33cab277d691ed5646bcd65 (patch)
tree3c04f6007840533e241fb54ca3a15728cb1a40f5 /gcc/value-range.cc
parent9ac9fde961f76879f0379ff3b2494a2f9ac915f7 (diff)
downloadgcc-f4dad09c543eebc4d33cab277d691ed5646bcd65.zip
gcc-f4dad09c543eebc4d33cab277d691ed5646bcd65.tar.gz
gcc-f4dad09c543eebc4d33cab277d691ed5646bcd65.tar.bz2
c++: modules ICE with typename friend
A couple of xtreme-header-* modules tests began ICEing in C++23 mode ever since r13-2650-g5d84a4418aa962 which introduced into <ranges> a dependently scoped friend declaration: friend /* typename */ _OuterIter::value_type; This happens because the streaming code assumes a TYPE_P friend must be a class type, but here it's a TYPENAME_TYPE, which doesn't have a TEMPLATE_INFO or CLASSTYPE_BEFRIENDING_CLASSES. This patch tries to correct this in a minimal way. gcc/cp/ChangeLog: * module.cc (friend_from_decl_list): Don't consider CLASSTYPE_TEMPLATE_INFO for a TYPENAME_TYPE friend. (trees_in::read_class_def): Don't add to CLASSTYPE_BEFRIENDING_CLASSES for a TYPENAME_TYPE friend. gcc/testsuite/ChangeLog: * g++.dg/modules/typename-friend_a.C: New test. * g++.dg/modules/typename-friend_b.C: New test.
Diffstat (limited to 'gcc/value-range.cc')
0 files changed, 0 insertions, 0 deletions