From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756046AbcGGBzH (ORCPT ); Wed, 6 Jul 2016 21:55:07 -0400 Received: from one.firstfloor.org ([193.170.194.197]:49767 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751504AbcGGBzF (ORCPT ); Wed, 6 Jul 2016 21:55:05 -0400 Date: Wed, 6 Jul 2016 18:55:01 -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] x86: remove LTO flags Message-ID: <20160707015500.GQ13997@two.firstfloor.org> References: <20160628004718.GS25646@wotan.suse.de> <1467850970-4063-1-git-send-email-mcgrof@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1467850970-4063-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 Wed, Jul 06, 2016 at 05:22:50PM -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. Sorry, the LTO flags are still needed. Please don't remove The 4.7 only workaround was only the LTO_REFERENCE_INITCALL macro, which can be removed (if LTO is not support 4.7 anymore) -Andi