https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40883
--- Comment #8 from joseph at codesourcery dot com <joseph at codesourcery dot com> --- Given how often such issues are in target-specific code, for targets that only get built as cross compilers, in practice we'll need someone building for all architectures *using a native compiler from the same trunk version, and configuring with --enable-werror-always* (whether with config-list.mk or otherwise) to detect such problems. That is, that will need doing both as a one-off to find problems now present that -Wformat-diag can detect, and subsequently at least every release cycle (preferably as a bot whose results are routinely monitored to detect problems soon after they are introduced). I know there are bots building GCC for lots of targets, but I don't know if any of the current bots build using current trunk GCC and using --enable-werror-always to detect such issues that otherwise only show up in a native bootstrap.
