https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83028
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |msebor at gcc dot gnu.org
Last reconfirmed| |2020-04-13
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
Confirmed. Unless the C++ 2a standard defines behavior in all cases issuing
the warning for both valid (in C++ 2a) and invalid code code on the bases that
it's invalid in some other standard or language, and without distinguishing
between the valid uses from the invalid ones, would make the warning
meaningless. At a minimum, the warning should be split into two: one for
portability to other standards/languages, and another for problems in C++ 2a.
