From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Emese Revfy <re.emese@gmail.com>,
Laura Abbott <labbott@redhat.com>,
PaX Team <pageexec@freemail.hu>,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] gcc-plugin-infrastructure updates for v4.8-rc2
Date: Mon, 8 Aug 2016 18:04:14 -0700 [thread overview]
Message-ID: <20160809010414.GA11494@www.outflux.net> (raw)
The following changes since commit 574673c231a5fad1560249cc3a598907acb36cf9:
printk: Remove unnecessary #ifdef CONFIG_PRINTK (2016-08-08 11:29:39 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/gcc-plugin-infrastructure-v4.8-rc2
for you to fetch changes up to caefd8c9a9fb06811e07bf3571e5d4450846b16a:
gcc-plugins: Add support for plugin subdirectories (2016-08-08 17:53:05 -0700)
----------------------------------------------------------------
Several fixes/improvements for the gcc plugin infrastructure:
- Fixes a problem with gcc plugins interfering with cc-option tests.
- Aborts more gracefully when gcc plugin headers or compiler support is
missing.
- Improves the gcc plugin rule generation to be more dynamic, pass arguments,
and build from subdirectories.
----------------------------------------------------------------
Emese Revfy (4):
kbuild: no gcc-plugins during cc-option tests
gcc-plugins: Add support for passing plugin arguments
gcc-plugins: Automate make rule generation
gcc-plugins: Add support for plugin subdirectories
Kees Cook (1):
gcc-plugins: abort builds cleanly when not supported
Makefile | 7 -------
scripts/Kbuild.include | 10 +++++++---
scripts/Makefile.gcc-plugins | 39 ++++++++++++++++++++++++++++-----------
scripts/gcc-plugin.sh | 14 ++++++++++++++
scripts/gcc-plugins/Makefile | 12 +++++++-----
5 files changed, 56 insertions(+), 26 deletions(-)
--
Kees Cook
Nexus Security
reply other threads:[~2016-08-09 1:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160809010414.GA11494@www.outflux.net \
--to=keescook@chromium.org \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pageexec@freemail.hu \
--cc=re.emese@gmail.com \
--cc=torvalds@linux-foundation.org \
/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).