I'd also like to point out that this is simply not a proper patch submission at all, independent of the specific issues about changes to prerequisites that require things to be raised and explained in a self-contained way on the gcc list. Every patch submission needs an explanation of the purpose of the patch - not just the ChangeLog entry saying at a low level what changed, but the higher-level motivation for why the patch was implemented and why it was implemented the way it was. It also needs to say how the patch was tested. And a multi-patch series should contain such an overview for the whole series (which might also make clear whether the patches were tested individually or only in combination), typically as patch 00/nn. Note that as stated in contribute.html this all applies even when the patch is being sent by a maintainer of the relevant part of the compiler.
-- Joseph S. Myers jos...@codesourcery.com
