[Bug c++/71267] [C++14] recursive metafunction won't compile: no type named 'type'

[Bug c++/71267] [C++14] recursive metafunction won't compile: no type named 'type'

[pinskia at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71267

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Known to fail|                            |10.3.0, 11.1.0
      Known to work|                            |11.2.0

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Looks fixed in GCC 11.2.0 and GCC12+.

[Bug c++/71267] [C++14] recursive metafunction won't compile: no type named 'type'

[redi at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71267

--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Accepted since r12-1094 and r11-8714:

c++: argument pack with expansion [PR86355]

This testcase revealed that we were using PACK_EXPANSION_EXTRA_ARGS a lot
more than necessary; use_pack_expansion_extra_args_p meant to use it in the
case of corresponding arguments in different argument packs differing in
whether they are pack expansions, but it was mistakenly also returning true
for the case of a single argument pack containing both expansion and
non-expansion elements.

Surprisingly, just disabling that didn't lead to any regressions in the
testsuite; it seems other changes have prevented us getting to this point
for code that used to exercise it.  So this patch limits the check to
arguments in the same position in the packs, and asserts that we never
actually see a mismatch.

PR c++/86355

gcc/cp/ChangeLog:

* pt.c (use_pack_expansion_extra_args_p): Don't compare
args from the same argument pack.

gcc/testsuite/ChangeLog:

* g++.dg/cpp0x/alias-decl-variadic2.C: New test.