From mboxrd@z Thu Jan 1 00:00:00 1970 Reply-To: kernel-hardening@lists.openwall.com Date: Wed, 16 Mar 2016 22:06:02 +0100 From: Emese Revfy Message-Id: <20160316220602.5269b38c162daa97f3cbe044@gmail.com> In-Reply-To: References: <20160307000208.1bec3e7dc874489d1b4fcbb4@gmail.com> <20160307000427.c82f18670568e1e656fc9532@gmail.com> <20160314215217.7fa20e0c85bfda75dc11b70c@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: [kernel-hardening] Re: [PATCH v5 2/5] GCC plugin infrastructure To: Masahiro Yamada Cc: Linux Kbuild mailing list , pageexec@freemail.hu, spender@grsecurity.net, kernel-hardening@lists.openwall.com, Michal Marek , Kees Cook , Rasmus Villemoes , fengguang.wu@intel.com, Dmitry Vyukov , Linux Kernel Mailing List List-ID: On Wed, 16 Mar 2016 16:41:36 +0900 Masahiro Yamada wrote: > > The scripts name also doesn't describe gcc plugins well. > > With my suggestion "scripts/gcc-plugins/", > the sub-directory name describes it very well. > > > > Plugins take part in the image building process > > in a different way than these tools and scripts do. > > Since there doesn't seen to be a good place for compiler plugins, maybe we should create a new toplevel directory > > called "build". Compiler plugins and other existing build tools could live there. What do you think? > > In my understanding, they are plug-in'ed into the cross-compiler that > compiles vmlinux. > > If so, GCC plugins should be happy in "scripts/" > because Kbuild descends into "scripts/" before building any objects for vmlinux. Ok, I'll move them under scripts/ in the next patch set. -- Emese