https://gcc.gnu.org/bugzilla/show_bug.cgi?id=124058
--- Comment #2 from Torbjorn SVENSSON <azoff at gcc dot gnu.org> --- (In reply to Richard Biener from comment #1) > Assuming trunk is also affected. Yes and no. In r16-6183-ge0fa6ea45fbd02, the default -std option was changed from 17 to 20, thus trunk reports this test as unsupported. However, if the test is ran with -std=gnu++17, then yes, the expected warnings are not generated.
