On Thu, Jun 9, 2016 at 10:37 AM, Emese Revfy <re.emese@xxxxxxxxx> wrote: > On Thu, 9 Jun 2016 12:57:16 +0200 > Michal Marek <mmarek@xxxxxxx> wrote: > >> Dne 9.6.2016 v 06:05 Stephen Rothwell napsal(a): >> > On Wed, 8 Jun 2016 19:56:38 -0700 Kees Cook <keescook@xxxxxxxxxxxx> wrote: >> >> Ah, yes, that should default to off. We'll get a fix landed ASAP. >> > >> > Note that this was an allmodconfig build. The default is 'n', but >> > allmodconfig will turn it on (as will allyesconfig). >> >> I guess we should make GCC_PLUGINS depend on !COMPILE_TEST. Actually I >> thought this was already the case, but it is not. > > Is it really necessary to disable all gcc plugins or would it be enough > to disable only the cyc_complexity plugin? I think disabling (depend on !COMPILE_TEST) plugins that have non-actionable output make sense. For example, in the future, things like constify or initify may produce warnings that are "real" in the sense that they have detected situations that should be fixed in the code. In a perfect world, we would include those fixes ahead of the new plugin to keep Stephen from going crazy. :) -Kees -- Kees Cook Chrome OS & Brillo Security -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
