https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111001
--- Comment #17 from Oleg Endo <olegendo at gcc dot gnu.org> --- (In reply to John Paul Adrian Glaubitz from comment #16) > Just saw the branch updates, thanks! FWIW, I did observe this issue in > gcc-13 only but not gcc-11 or gcc-12. But that might be owed to the fact > that Debian's gcc-11 and gcc-12 packages had not received the latest branch > updates yet. Yes, I know it has been observed on the latest GCC-13 only. It was an oversight in the code from the beginning, which got triggered by another change in the compiler. I haven't checked which change exactly, but I guess it must have been some backported change. So if the same/similar thing gets backported to GCC-11 or GCC-12 it might trigger this bug there, too. Hence the preventive measure. It's a rather obvious bug/fix, so should be safe.
