Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932782AbcLHTAw (ORCPT ); Thu, 8 Dec 2016 14:00:52 -0500 Received: from mail-io0-f170.google.com ([209.85.223.170]:36820 "EHLO mail-io0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932291AbcLHTAt (ORCPT ); Thu, 8 Dec 2016 14:00:49 -0500 MIME-Version: 1.0 From: Kees Cook Date: Thu, 8 Dec 2016 11:00:42 -0800 Message-ID: Subject: enabling COMPILE_TEST support for GCC plugins in v4.11 To: Stephen Rothwell , Arnd Bergmann , Randy Dunlap , Olof Johansson , Mark Brown , info@kernelci.org, Linus Torvalds , Andrew Morton , Will Deacon , Russell King - ARM Linux Cc: LKML , Linux-Next , Fengguang Wu , Andrew Donnellan , Michael Ellerman , Laura Abbott , "x86@kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1763 Lines: 41 Hi, I'd like to get the GCC plugins building under allyesconfig/allmodconfig for -next soon (with the intention of landing the change in v4.11). Specifically, I intend to revert a519167e753e ("gcc-plugins: disable under COMPILE_TEST"). Right now the plugins are only supported on x86, arm, and arm64, though powerpc may happen in either v4.10 or v4.11 as well. This means that the autobuilders for these architectures need to have the "gcc plugin development" package installed which contains the GCC headers needed for the plugins. For Debian/Ubuntu, this is gcc-$N-plugin-dev (and for cross compilers: gcc-$N-plugin-dev-$arch-linux-$abi). For Fedora, it is gcc-plugin-devel (though I'm not sure the naming for cross compilers). Manual builds of compilers should already have these headers installed. The "noisy" plugin, cyc_complexity, is just an example, and I have disabled it (which is pending[1] for v4.10). The remaining ones (sancov and latent_entropy) are what I'm hoping to see tested tree-wide (with the expectation that more are coming down the road: initify, randstruct, structleak, constify, ...) IIUC, the 0day builder already has the headers installed. I tried to look through linux-next to find all the other folks that do autobuilding on these architectures; apologies if I've missed anyone. If you have a moment, applying 215e2aa6c024[1] and reverting a519167e753e for an allyesconfig/allmodconfig build should let you know if things are working correctly with headers installed. If anyone sees any problems, please let me know and I can queue up fixes. Thanks! -Kees [1] http://git.kernel.org/cgit/linux/kernel/git/kees/linux.git/commit/?h=for-next/gcc-plugins&id=215e2aa6c024d27cdbe88e2ea88cb59dcab588eb -- Kees Cook Nexus Security