https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120012
--- Comment #3 from Jason Merrill <jason at gcc dot gnu.org> --- (In reply to Richard Biener from comment #2) > going to be interesting to decide what to do on branches ... does it affect > the ABI of any part of libstdc++, in the shared object or instantiated > templates in libraries using libstdc++? It seems not to affect libstdc++; the warning I've implemented doesn't fire when building the shared object or running the testsuite. On branches I'm thinking to give the warning under -Wabi=0. It's awkward that plain -Wabi currently gives a warning, though that could change. I suppose we could also add non-default -fabi-version=21 to GCC 15 for only this change, and bump other GCC 16 changes to 22, but I'm not sure how worthwhile that would be. I don't think we can change the default GCC 15 ABI at this point.
