From: Emese Revfy <re.emese@gmail.com>
To: linux-kbuild@vger.kernel.org
Cc: pageexec@freemail.hu, spender@grsecurity.net,
kernel-hardening@lists.openwall.com, mmarek@suse.com,
keescook@chromium.org, linux@rasmusvillemoes.dk
Subject: [PATCH v3 0/3] Introduce GCC plugin infrastructure
Date: Mon, 22 Feb 2016 20:13:35 +0100 [thread overview]
Message-ID: <20160222201335.449323716ca4d929f92424d5@gmail.com> (raw)
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 architecture enables plugins.
This infrastructure was ported from grsecurity/PaX. It is a CII project
supported by the Linux Foundation.
Emese Revfy (3):
GCC plugin infrastructure
Add Cyclomatic complexity plugin
Documentations of the GCC plugin infrastructre
Changes from v2:
* Fixed incorrectly encoded characters
* Generate the GIMPLE, IPA, SIMPLE_IPA and RTL pass structures
(Suggested-by: Rasmus Villemoes <linux@rasmusvillemoes.dk>)
* Write plugin related warning messages to stderr instead of stdout
(Suggested-by: Kees Cook <keescook@chromium.org>)
* Mention the installation of the gcc plugin headers (Documentation)
Changes from v1:
* Move the gcc-plugins make target into a separate Makefile because there may
be a lot of plugins (Suggested-by: Rasmus Villemoes)
* Simplify the dependencies of the plugin related config option
(Suggested-by: Kees Cook <keescook@chromium.org>)
* Removed the unnecessary example plugin
---
Documentation/dontdiff | 1 +
Documentation/gcc-plugins.txt | 80 ++++
Makefile | 41 +-
arch/Kconfig | 24 +
arch/x86/Kconfig | 1 +
init/Makefile | 3 +
scripts/Makefile.build | 2 +-
scripts/Makefile.clean | 3 +-
scripts/Makefile.gcc-plugins | 30 ++
scripts/Makefile.host | 69 ++-
scripts/gcc-plugin.sh | 51 ++
scripts/link-vmlinux.sh | 2 +-
scripts/package/builddeb | 1 +
tools/gcc/Makefile | 19 +
tools/gcc/cyc_complexity_plugin.c | 70 +++
tools/gcc/gcc-common.h | 794 +++++++++++++++++++++++++++++++
tools/gcc/gcc-generate-gimple-pass.h | 172 +++++++
tools/gcc/gcc-generate-ipa-pass.h | 286 +++++++++++
tools/gcc/gcc-generate-rtl-pass.h | 172 +++++++
tools/gcc/gcc-generate-simple_ipa-pass.h | 172 +++++++
20 files changed, 1978 insertions(+), 15 deletions(-)
next reply other threads:[~2016-02-22 19:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 19:13 Emese Revfy [this message]
2016-02-22 19:14 ` [PATCH v3 1/3] GCC plugin infrastructure Emese Revfy
2016-02-22 19:16 ` [PATCH v3 2/3] Add Cyclomatic complexity GCC plugin Emese Revfy
2016-02-22 19:17 ` [PATCH v3 3/3] Documentation for the GCC plugin infrastructure Emese Revfy
2016-02-23 0:20 ` [PATCH v3 0/3] Introduce " Kees Cook
2016-02-24 22:26 ` Emese Revfy
2016-02-24 22:48 ` Kees Cook
2016-02-25 22:45 ` Emese Revfy
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=20160222201335.449323716ca4d929f92424d5@gmail.com \
--to=re.emese@gmail.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mmarek@suse.com \
--cc=pageexec@freemail.hu \
--cc=spender@grsecurity.net \
/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