From: "PaX Team" <pageexec@freemail.hu>
To: David Brown <david.brown@linaro.org>, Jeff Law <law@redhat.com>,
Kees Cook <keescook@chromium.org>
Cc: Emese Revfy <re.emese@gmail.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Michal Marek <mmarek@suse.com>,
linux-kbuild <linux-kbuild@vger.kernel.org>,
Brad Spengler <spender@grsecurity.net>,
"kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Fengguang Wu <fengguang.wu@intel.com>,
Dmitry Vyukov <dvyukov@google.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 0/6] Introduce GCC plugin infrastructure
Date: Tue, 12 Apr 2016 23:26:48 +0200 [thread overview]
Message-ID: <570D6818.30507.4DB19537@pageexec.freemail.hu> (raw)
In-Reply-To: <CAGXu5jLEui=E22t5=tSNG2nOA7LWO4UNuVknhteTxEZzY+iwyg@mail.gmail.com>
On 12 Apr 2016 at 12:46, Kees Cook wrote:
> Looks like it's in the upstream tree:
>
> https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=bfe972081c3c75019fa5a6e883dcbeb5e03eea18
>
> I'm not sure how GCC does bug fix releases. Is this going to be in 5.4
> or 5.3.1? (Is there such a thing as 5.3.1 planned?) I've CCed Jeff in
> case he's got a moment to peek at this.
gcc-5 will be maintained until gcc-7 (due in a year) so this commit will end up in
the next minor release (5.4) eventually.
next prev parent reply other threads:[~2016-04-12 21:28 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 ` [PATCH v6 0/6] Introduce GCC plugin infrastructure David Brown
2016-04-12 18:27 ` Kees Cook
2016-04-12 18:41 ` David Brown
2016-04-12 19:46 ` Kees Cook
2016-04-12 21:26 ` PaX Team [this message]
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=570D6818.30507.4DB19537@pageexec.freemail.hu \
--to=pageexec@freemail.hu \
--cc=david.brown@linaro.org \
--cc=dvyukov@google.com \
--cc=fengguang.wu@intel.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=law@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mmarek@suse.com \
--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