From: Andi Kleen <andi@firstfloor.org>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: Andi Kleen <andi@firstfloor.org>,
"H. Peter Anvin" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
X86 ML <x86@kernel.org>, Borislav Petkov <bp@alien8.de>,
Andy Lutomirski <luto@amacapital.net>
Subject: Re: Is LTO_REFERENCE_INITCALL() still needed?
Date: Fri, 24 Jun 2016 14:07:53 -0700 [thread overview]
Message-ID: <20160624210753.GA13997@two.firstfloor.org> (raw)
In-Reply-To: <CAB=NE6W6Eh1tU=NXf20f-CPYeT22mtXGzrYqM9W-f14dGBrEsA@mail.gmail.com>
> But nothing quite obviously setting these upstream. I'm probably just
> missing something obvious though. Either way I figured now would be a
> good time to ask as I have other code that would use this, the linker
> table stuff I've been working. If we can avoid propagating more use of
> LTO_REFERENCE_INITCALL() then great. If we still need it its probably
> good to document this a bit more as can't see anything super clear.
It was a work around for a gcc 4.7 LTO problem. I guess it could be
dropped by now.
Yes I've been slow in submitting the LTO patches, even though they
have a quite active out of tree user base. Will try to do better.
-Andi
next prev parent reply other threads:[~2016-06-24 21:07 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 [this message]
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
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=20160624210753.GA13997@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mcgrof@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).