https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109717
--- Comment #3 from Paul Smith <psmith at gnu dot org> --- OK, well, we don't have to say "broken"; all I know is that perfectly respectable code that used to work without triggering these warnings in older versions of GCC, and with older -std=c++..., is now failing in GCC 13.1 / -std=c++20 widely enough that I must disable these warnings, which is unfortunate.
