On 17 Dec 2016, at 12:46, David Chisnall <thera...@freebsd.org> wrote: > > On 16 Dec 2016, at 19:31, Baptiste Daroussin <b...@freebsd.org> wrote: >> >> Other than that, it makes more difficult to use vanilla gcc with out >> userland. >> and it is adding more complexity to be able to build freebsd from a non >> freebsd >> system which some people are working on. > > Why? You’ll get some spurious warnings about printf, but that’s all.
Unfortunately, we compile large parts of the tree with -Werror. Thus, "spurious warnings" will break the build, leaving the user two options: disabling -Wformat warnings, or disabling -Werror altogether, neither of which are very recommendable. As far as I know, there is no -Wno-error-on-undefined-printf-specifiers. It would also be hard to implement, since after any undefined specifiers have been encountered, you cannot reason about the following ones anymore either. IMHO, if people want to use non-standard specifiers, let them define their own almost_printf_but_not_quite() functions, and forgo any format checking. -Dimitry
signature.asc
Description: Message signed with OpenPGP using GPGMail
