https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64271
--- Comment #14 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Roland Illig from comment #12) > After all, these patches are only a suggestion how GCC _might_ be fixed. Which is exactly why patches should go to the mailing lists. The reviewer might request changes to the patch, so the submitter will be asked to make changes and re-test the patch to ensure it still works and fixes the problem. The reviewer doesn't necessarily have access to the right systems to test the patch themselves. That process of iteratively refining the patch belongs on the mailing lists, not in bugzilla.