On Jan 30, 2019, Alexandre Oliva <aol...@redhat.com> wrote: > Because of rank compares, and checks for ck_list, we know that if we > see user_conv_p or ck_list in ics1, we'll also see it in ics2. This > reasoning does not extend to ck_aggr, however, so we might have > ck_aggr conversions starting both ics1 and ics2, which we handle > correctly, or either, which we likely handle by crashing on whatever > path we take depending on whether ck_aggr is in ics1 or ics2. [...]
Ping? https://gcc.gnu.org/ml/gcc-patches/2019-01/msg01731.html > for gcc/cp/ChangeLog > PR c++/86218 > * call.c (compare_ics): Deal with ck_aggr in either cs. > for gcc/testsuite/ChangeLog > PR c++/86218 > * g++.dg/cpp0x/pr86218.C: New. -- 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
