https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84478
--- Comment #7 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> --- > --- Comment #6 from Martin Sebor <msebor at gcc dot gnu.org> --- > If this is a new regression please open a new bug for it. It's probably a How would I determine that? The testcase fails on a considerable number of targets the moment it is introduced. > fallout from r267503 or one of the other related changes. And what would be the point anyway: either the testcase doesn't always test what it claims to or the patch doesn't always fix what it should. In either case, the author is on the hook to investigate and fix the issue, both well within the scope of this PR. Only if it turns out that this is a completely different issue that needs to be fixed without modifying either the new testcase or the rest of the patch can a new PR be opened. Everything else only leads to a needless explosion of PRs.
