Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1757845AbcDLV2U (ORCPT <rfc822;w@1wt.eu>);
	Tue, 12 Apr 2016 17:28:20 -0400
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 <rfc822;linux-kernel@vger.kernel.org>);
	Tue, 12 Apr 2016 17:28:17 -0400
From: "PaX Team" <pageexec@freemail.hu>
To: David Brown <david.brown@linaro.org>, Jeff Law <law@redhat.com>,
        Kees Cook <keescook@chromium.org>
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
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>
Message-ID: <570D6818.30507.4DB19537@pageexec.freemail.hu>
In-reply-to: <CAGXu5jLEui=E22t5=tSNG2nOA7LWO4UNuVknhteTxEZzY+iwyg@mail.gmail.com>
References: <20160407231023.5f1307ffc79f0cdd880eedb7@gmail.com>, <20160412184147.GA92432@davidb.org>, <CAGXu5jLEui=E22t5=tSNG2nOA7LWO4UNuVknhteTxEZzY+iwyg@mail.gmail.com>
X-mailer: Pegasus Mail for Windows (4.71.565)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.12 (r00tworld.com [212.85.137.150]); Tue, 12 Apr 2016 23:26:36 +0200 (CEST)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 494
Lines: 12

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.