From: Alexey Kardashevskiy <aik@linux.ibm.com>
To: Alan Modra <amodra@gmail.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 20:33:37 +1100 [thread overview]
Message-ID: <5aa60950-d93c-f700-3b0b-a01f947e8a22@linux.ibm.com> (raw)
In-Reply-To: <20210310050722.GN6042@bubble.grove.modra.org>
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?
On 10/03/2021 16:07, Alan Modra wrote:
> On Wed, Mar 10, 2021 at 03:44:44PM +1100, Alexey Kardashevskiy wrote:
>> For my own education, is .got for prom_init.o still generated by ld or gcc?
>
> .got is generated by ld.
>
>> In other words, should "objdump -D -s -j .got" ever dump .got for any .o
>> file, like below?
>
> No. "objdump -r prom_init.o | grep GOT" will tell you whether
> prom_init.o *may* cause ld to generate .got entries. (Linker
> optimisations or --gc-sections might remove the need for those .got
> entries.)
>
>> objdump: section '.got' mentioned in a -j option, but not found in any input
>> file
>
> Right, expected.
>
--
Alexey Kardashevskiy
IBM OzLabs, LTC Team
e-mail: aik@linux.ibm.com
next prev parent reply other threads:[~2021-03-10 9:43 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 [this message]
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
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=5aa60950-d93c-f700-3b0b-a01f947e8a22@linux.ibm.com \
--to=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).