From: Emese Revfy <re.emese@gmail.com>
To: Kees Cook <keescook@chromium.org>
Cc: linux-kbuild <linux-kbuild@vger.kernel.org>,
PaX Team <pageexec@freemail.hu>,
Brad Spengler <spender@grsecurity.net>,
"kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>,
Michal Marek <mmarek@suse.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>
Subject: [kernel-hardening] Re: [PATCH v2 1/3] GCC plugin infrastructure
Date: Thu, 18 Feb 2016 22:21:55 +0100 [thread overview]
Message-ID: <20160218222155.85bf19be5ab9c48efc2fec66@gmail.com> (raw)
In-Reply-To: <CAGXu5jJcxDObPaVN25Keru6Gj9jo=EgvzhrLUUPcC0pki8pp_g@mail.gmail.com>
> > +ifeq ($(call cc-ifversion, -ge, 0408, y), y)
> > + $(CONFIG_SHELL) -x $(srctree)/scripts/gcc-plugin.sh "$(HOSTCXX)" "$(HOSTCXX)" "$(CC)"
> > +else
> > + $(CONFIG_SHELL) -x $(srctree)/scripts/gcc-plugin.sh "$(HOSTCC)" "$(HOSTCXX)" "$(CC)"
>
> Is there a reason for these to be running with -x? This makes it noisy
> when running with V=0 (the default).
I think -x is useful, it prints out e.g., which headers are missing. gcc-plugin.sh with -x runs
only when there is something wrong (as you can see it in the kbuild test bot mails).
--
Emese
next prev parent reply other threads:[~2016-02-18 21:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 22:36 [kernel-hardening] [PATCH v2 0/3] Introduce GCC plugin infrastructure Emese Revfy
2016-02-11 22:39 ` [kernel-hardening] [PATCH v2 1/3] " Emese Revfy
2016-02-18 0:18 ` [kernel-hardening] " Kees Cook
2016-02-18 21:21 ` Emese Revfy [this message]
2016-02-11 22:41 ` [kernel-hardening] [PATCH v2 2/3] Add Cyclomatic complexity GCC plugin Emese Revfy
2016-02-18 0:27 ` [kernel-hardening] " Kees Cook
2016-02-18 21:32 ` Emese Revfy
2016-02-11 22:43 ` [kernel-hardening] [PATCH v2 3/3] Documentation for the GCC plugin infrastructure Emese Revfy
2016-02-18 0:35 ` [kernel-hardening] " Kees Cook
2016-02-18 22:13 ` 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=20160218222155.85bf19be5ab9c48efc2fec66@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;
as well as URLs for NNTP newsgroup(s).