mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: "Luis R. Rodriguez" <mcgrof@kernel.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()
Date: Thu, 21 Jul 2016 21:00:03 +0200	[thread overview]
Message-ID: <20160721190003.GB32299@wotan.suse.de> (raw)
In-Reply-To: <20160707163159.GR13997@two.firstfloor.org>

On Thu, Jul 07, 2016 at 09:32:00AM -0700, Andi Kleen wrote:
> 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 <ak@linux.intel.com>

This is not yet merged but since it makes more sense in the
context of linker tables I'm going to fold this patch into
that series and post today.

  Luis

      reply	other threads:[~2016-07-21 19:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-23 23:34 Is LTO_REFERENCE_INITCALL() still needed? Luis R. Rodriguez
2016-06-24 21:07 ` Andi Kleen
2016-06-28  0:47   ` Luis R. Rodriguez
2016-07-07  0:22     ` [PATCH] x86: remove LTO flags Luis R. Rodriguez
2016-07-07  1:55       ` Andi Kleen
2016-07-07 16:01         ` [PATCH v2] x86: remove LTO_REFERENCE_INITCALL() Luis R. Rodriguez
2016-07-07 16:32           ` Andi Kleen
2016-07-21 19:00             ` Luis R. Rodriguez [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160721190003.GB32299@wotan.suse.de \
    --to=mcgrof@kernel.org \
    --cc=andi@firstfloor.org \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®