Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 16 Mar 2016 22:06:02 +0100
From: Emese Revfy <>
To: Masahiro Yamada <>
Cc: Linux Kbuild mailing list <>,,,, Michal Marek <>, Kees
 Cook <>, Rasmus Villemoes <>,, Dmitry Vyukov <>, Linux Kernel
 Mailing List <>
Subject: Re: [PATCH v5 2/5] GCC plugin infrastructure

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.


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.