From: Alan Modra <amodra@gmail.com>
To: Fangrui Song <i@maskray.me>
Cc: binutils@sourceware.org
Subject: Re: [PowerPC] Garbage collecting .toc entries in a non-adhoc way (section group)
Date: Wed, 04 Mar 2020 01:25:00 -0000 [thread overview]
Message-ID: <20200304012543.GS5384@bubble.grove.modra.org> (raw)
In-Reply-To: <BY5PR07MB73163B2589E96E97B635FC35CBE40@BY5PR07MB7316.namprd07.prod.outlook.com>
On Mon, Mar 02, 2020 at 06:02:41PM -0800, Fangrui Song wrote:
> Thanks for the confirmation that switching to @got may be beneficial.
> Is there any drawback?
The TOC scheme may give better locality of reference and thus better
cache performance. The TOC layout is under control of the compiler,
which generally has better information about data access patterns than
the linker. Mind you, powerpc gcc doesn't really do anything about
optimising the TOC, but it would be possible.
> If you think @got is good
Yes, I do.
--
Alan Modra
Australia Development Lab, IBM
prev parent reply other threads:[~2020-03-04 1:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 6:56 Fangrui Song
2020-03-02 10:59 ` Alan Modra
2020-03-02 18:03 ` Fangrui Song
2020-03-02 22:50 ` Alan Modra
2020-03-03 2:03 ` Fangrui Song
2020-03-04 1:25 ` Alan Modra [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=20200304012543.GS5384@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=i@maskray.me \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).