[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20160316220602.5269b38c162daa97f3cbe044@gmail.com>
Date: Wed, 16 Mar 2016 22:06:02 +0100
From: Emese Revfy <re.emese@...il.com>
To: Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc: Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
pageexec@...email.hu, spender@...ecurity.net,
kernel-hardening@...ts.openwall.com, Michal Marek <mmarek@...e.com>, Kees
Cook <keescook@...omium.org>, Rasmus Villemoes <linux@...musvillemoes.dk>,
fengguang.wu@...el.com, Dmitry Vyukov <dvyukov@...gle.com>, Linux Kernel
Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v5 2/5] GCC plugin infrastructure
On Wed, 16 Mar 2016 16:41:36 +0900
Masahiro Yamada <yamada.masahiro@...ionext.com> 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
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
