From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Michael Ellerman <ellerman@au1.ibm.com>,
Alan Modra <amodra@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: alexey@au1.ibm.com, Alexey Kardashevskiy <aik@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: PowerPC64 future proof kernel toc, revised for lld
Date: Fri, 12 Mar 2021 14:45:13 +1100 [thread overview]
Message-ID: <15227114-a5fc-9573-f563-cde1b84cbaa1@ozlabs.ru> (raw)
In-Reply-To: <87mtv9jmgf.fsf@mpe.ellerman.id.au>
On 12/03/2021 10:32, Michael Ellerman wrote:
> Alan Modra <amodra@gmail.com> writes:
>> On Wed, Mar 10, 2021 at 01:44:57PM +0100, Christophe Leroy wrote:
>>>
>>> Le 10/03/2021 à 13:25, Alan Modra a écrit :
>>>> On Wed, Mar 10, 2021 at 08:33:37PM +1100, Alexey Kardashevskiy wrote:
>>>>> One more question - the older version had a construct "DEFINED (.TOC.) ?
>>>>> .TOC. : ..." in case .TOC. is not defined (too old ld? too old gcc?) but the
>>>>> newer patch seems assuming it is always defined, when was it added? I have
>>>>> the same check in SLOF, for example, do I still need it?
>>>>
>>>> .TOC. symbol support was first added 2012-11-06, so you need
>>>> binutils-2.24 or later to use .TOC. as a symbol.
>>>>
>>>
>>> As of today, minimum requirement to build kernel is binutils 2.23, see https://urldefense.proofpoint.com/v2/url?u=https-3A__www.kernel.org_doc_html_latest_process_changes.html-23current-2Dminimal-2Drequirements&d=DwIDAw&c=jf_iaSHvJObTbx-siA1ZOg&r=uzpscot8Q8p-51o1Gp1vnzKV94bfny2qmUdVe821lv0&m=SYi605mn0I1hf1QoHuvHXtS_Z-R6JJHbzS34cEtV2Tk&s=47ckf3yxVcP6RwRb8D9viYOQSWpf6rXrnWj4YM4OTJ0&e=
>>
>> Yes, and arch/powerpc/Makefile complains about 2.24. So for powerpc
>> that means you need to go to at least 2.25.
>
> Not quite. It only complains for little endian builds, and only if you
> have stock 2.24, it will allow a 2.24.<something>.
>
> I do most of my builds with 2.34, so I have no issue with newer
> binutils. But we try not to increase the minimum version too rapidly to
> accommodate folks using older and/or "Enterprise" distros that are stuck
> on old toolchains.
>
> I think we are within our rights to increase the minimum requirement for
> powerpc builds, if it brings advantages we can identify.
>
> The way to do that would be to add a new check in our arch Makefile that
> rejects the older versions.
The upstream llvm just learnt to handle the .TOC. symbol in linker
scripts so we may delay the future for a bit longer :) @dja wanted
upstream llvm anyway and the currently supported llvm 10.xx is not much
value for our experiments.
https://github.com/llvm/llvm-project/commit/e4f385d89448393b4d213339bbbbbbaa42b49489
--
Alexey
prev parent reply other threads:[~2021-03-12 3:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 4:56 PowerPC64 future proof kernel toc, revised Alan Modra
2021-03-10 3:48 ` PowerPC64 future proof kernel toc, revised for lld Alan Modra
2021-03-10 4:44 ` Alexey Kardashevskiy
2021-03-10 5:07 ` Alan Modra
2021-03-10 9:33 ` Alexey Kardashevskiy
2021-03-10 12:25 ` Alan Modra
2021-03-10 12:44 ` Christophe Leroy
2021-03-10 16:17 ` Segher Boessenkool
2021-03-10 23:41 ` Alan Modra
2021-03-11 23:32 ` Michael Ellerman
2021-03-12 3:45 ` Alexey Kardashevskiy [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=15227114-a5fc-9573-f563-cde1b84cbaa1@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=aik@linux.ibm.com \
--cc=alexey@au1.ibm.com \
--cc=amodra@gmail.com \
--cc=christophe.leroy@csgroup.eu \
--cc=ellerman@au1.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.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).