[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <570D6818.30507.4DB19537@pageexec.freemail.hu>
Date: Tue, 12 Apr 2016 23:26:48 +0200
From: "PaX Team" <pageexec@...email.hu>
To: David Brown <david.brown@...aro.org>, Jeff Law <law@...hat.com>,
Kees Cook <keescook@...omium.org>
CC: Emese Revfy <re.emese@...il.com>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Michal Marek <mmarek@...e.com>,
linux-kbuild <linux-kbuild@...r.kernel.org>,
Brad Spengler <spender@...ecurity.net>,
"kernel-hardening@...ts.openwall.com"
<kernel-hardening@...ts.openwall.com>,
Rasmus Villemoes <linux@...musvillemoes.dk>,
Fengguang Wu <fengguang.wu@...el.com>,
Dmitry Vyukov <dvyukov@...gle.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v6 0/6] Introduce GCC plugin infrastructure
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.
Powered by blists - more mailing lists