From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752384AbcGGQcG (ORCPT ); Thu, 7 Jul 2016 12:32:06 -0400 Received: from one.firstfloor.org ([193.170.194.197]:51678 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751344AbcGGQcE (ORCPT ); Thu, 7 Jul 2016 12:32:04 -0400 Date: Thu, 7 Jul 2016 09:32:00 -0700 From: Andi Kleen To: "Luis R. Rodriguez" Cc: andi@firstfloor.org, hpa@zytor.com, linux-kernel@vger.kernel.org, x86@kernel.org, bp@alien8.de, luto@amacapital.net Subject: Re: [PATCH v2] x86: remove LTO_REFERENCE_INITCALL() Message-ID: <20160707163159.GR13997@two.firstfloor.org> References: <20160707015500.GQ13997@two.firstfloor.org> <1467907309-6678-1-git-send-email-mcgrof@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1467907309-6678-1-git-send-email-mcgrof@kernel.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 07, 2016 at 09:01:49AM -0700, Luis R. Rodriguez wrote: > The setup for LTO never made it upstream, and although this has > some users, this is now really old stuff for a gcc 4.7 LTO problem. > We know that at least LTO_REFERENCE_INITCALL() work around can > be removed if LTO is not supported on v4.7 anymore. > > As per Andi the DISABLE_LTO and LTO_CFLAGS are still neeeded though. Looks good. Thanks Acked-by: Andi Kleen -Andi