From: David Brown <david.brown@linaro.org>
To: Emese Revfy <re.emese@gmail.com>
Cc: linux-kbuild@vger.kernel.org, pageexec@freemail.hu,
spender@grsecurity.net, kernel-hardening@lists.openwall.com,
mmarek@suse.com, keescook@chromium.org, linux@rasmusvillemoes.dk,
fengguang.wu@intel.com, dvyukov@google.com,
linux-kernel@vger.kernel.org, yamada.masahiro@socionext.com
Subject: Re: [PATCH v6 0/6] Introduce GCC plugin infrastructure
Date: Tue, 12 Apr 2016 11:46:07 -0600 [thread overview]
Message-ID: <20160412174607.GA92143@davidb.org> (raw)
In-Reply-To: <20160407231023.5f1307ffc79f0cdd880eedb7@gmail.com>
On Thu, Apr 07, 2016 at 11:10:23PM +0200, Emese Revfy wrote:
>This patch set introduce the GCC plugin infrastructure with examples for testing
>and documentation.
>
>GCC plugins are loadable modules that provide extra features to the compiler.
>They are useful for runtime instrumentation and static analysis.
>
>The infrastructure supports all gcc versions from 4.5 to 6.0, building
>out-of-tree modules and building in a separate directory. Cross-compilation
>is supported too but currently only the x86, arm and arm64 architectures enables plugins.
>
>This infrastructure was ported from grsecurity/PaX. It is a CII project
>supported by the Linux Foundation.
>
>Emese Revfy (6):
> Shared library support
> GCC plugin infrastructure
> The GCC plugin infrastructure supports the arm and arm64 architectures too
> Add Cyclomatic complexity plugin
> Documentations of the GCC plugin infrastructre
> Add sancov plugin
I've tested the v6 patches on arm, and partially on arm64. The arm64
gcc has a bug in make install that doesn't install all necessary
headers to build plugins. I believe the patch will work once that
version gets out. It does, however, print a helpful message now
explaining the likely cause of the failure.
Tested-by: David Brown <david.brown@linaro.org>
next prev parent reply other threads:[~2016-04-12 17:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 21:10 [PATCH v6 0/6] Introduce GCC plugin infrastructure Emese Revfy
2016-04-07 21:11 ` [PATCH v6 1/6] Shared library support Emese Revfy
2016-04-07 21:13 ` [PATCH v6 2/6] GCC plugin infrastructure Emese Revfy
2016-04-13 2:35 ` Masahiro Yamada
2016-04-21 16:55 ` Kees Cook
2016-04-07 21:15 ` [PATCH v6 3/6] The GCC plugin infrastructure supports the arm and arm64 architectures too Emese Revfy
2016-04-07 21:16 ` [PATCH v6 4/6] Add Cyclomatic complexity GCC plugin Emese Revfy
2016-04-07 21:17 ` [PATCH v6 5/6] Documentation for the GCC plugin infrastructure Emese Revfy
2016-04-07 21:19 ` [PATCH v6 6/6] Add sancov plugin Emese Revfy
2016-04-12 17:46 ` David Brown [this message]
2016-04-12 18:27 ` [PATCH v6 0/6] Introduce GCC plugin infrastructure Kees Cook
2016-04-12 18:41 ` David Brown
2016-04-12 19:46 ` Kees Cook
2016-04-12 21:26 ` PaX Team
2016-04-12 18:52 ` Emese Revfy
2016-04-12 19:47 ` Kees Cook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160412174607.GA92143@davidb.org \
--to=david.brown@linaro.org \
--cc=dvyukov@google.com \
--cc=fengguang.wu@intel.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mmarek@suse.com \
--cc=pageexec@freemail.hu \
--cc=re.emese@gmail.com \
--cc=spender@grsecurity.net \
--cc=yamada.masahiro@socionext.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).