public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Alan Modra <amodra@gmail•com>
To: 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 15:37:22 +1030	[thread overview]
Message-ID: <20210310050722.GN6042@bubble.grove.modra.org> (raw)
In-Reply-To: <3c92968f-7c61-8d36-4001-91f8630de4b1@linux.ibm.com>

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.

-- 
Alan Modra
Australia Development Lab, IBM

  reply	other threads:[~2021-03-10  5:07 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 [this message]
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

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=20210310050722.GN6042@bubble.grove.modra.org \
    --to=amodra@gmail$(echo .)com \
    --cc=aik@linux$(echo .)ibm.com \
    --cc=alexey@au1$(echo .)ibm.com \
    --cc=ellerman@au1$(echo .)ibm.com \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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