From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from r00tworld.com ([212.85.137.150]:39839 "EHLO r00tworld.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754251AbcDLV2R (ORCPT ); Tue, 12 Apr 2016 17:28:17 -0400 From: "PaX Team" Date: Tue, 12 Apr 2016 23:26:48 +0200 MIME-Version: 1.0 Subject: Re: [PATCH v6 0/6] Introduce GCC plugin infrastructure Reply-to: pageexec@freemail.hu Message-ID: <570D6818.30507.4DB19537@pageexec.freemail.hu> In-reply-to: References: <20160407231023.5f1307ffc79f0cdd880eedb7@gmail.com>, <20160412184147.GA92432@davidb.org>, Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Sender: linux-kbuild-owner@vger.kernel.org List-ID: To: David Brown , Jeff Law , Kees Cook Cc: Emese Revfy , Masahiro Yamada , Michal Marek , linux-kbuild , Brad Spengler , "kernel-hardening@lists.openwall.com" , Rasmus Villemoes , Fengguang Wu , Dmitry Vyukov , LKML 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.