From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Alan Modra <amodra@gmail.com>, Alexey Kardashevskiy <aik@linux.ibm.com>
Cc: alexey@au1.ibm.com, linuxppc-dev@lists.ozlabs.org, ellerman@au1.ibm.com
Subject: Re: PowerPC64 future proof kernel toc, revised for lld
Date: Wed, 10 Mar 2021 13:44:57 +0100 [thread overview]
Message-ID: <df863fb6-2fd6-00d7-b6f3-94a49c2a5405@csgroup.eu> (raw)
In-Reply-To: <20210310122513.GB29645@bubble.grove.modra.org>
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://www.kernel.org/doc/html/latest/process/changes.html#current-minimal-requirements
Christophe
next prev parent reply other threads:[~2021-03-10 12: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 [this message]
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
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=df863fb6-2fd6-00d7-b6f3-94a49c2a5405@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=aik@linux.ibm.com \
--cc=alexey@au1.ibm.com \
--cc=amodra@gmail.com \
--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).