public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Tom Kacvinsky <tkacvins@gmail.com>
To: Binutils <binutils@sourceware.org>
Subject: Re: Question about readelf output from shared library built with lld, gold, and bfd linkers
Date: Mon, 21 Nov 2022 12:43:20 -0500	[thread overview]
Message-ID: <CAG_eJLcYkaC_UP5YXxZF8JFnwGjC9d_SnWAfEgxMAq2rYO2KXA@mail.gmail.com> (raw)
In-Reply-To: <ef554690-7a88-b2c4-453d-78714ad93451@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 840 bytes --]

On Mon, Nov 21, 2022 at 11:48 AM Nick Clifton <nickc@redhat.com> wrote:

> Hi Tom,
>
> > Also, a question: would -z combreloc make a difference with relocations
> at
> > startup?  I was just perusing the ld manual and ran across that.
>
> It may well do.  It is certainly worth a try.
>

Alas, no joy.  These are the types of fun problems I face at work - change
one of the tools
we use to build our product and one of our performance tests has a
regression.  Then it
is on me to figure out why.  But, to be honest, this is black magic to me.
I do not know
where to start looking to figure out why lld generates the final ELF file
that runs quicker
than what is generated by the gold linker.

So, I guess the next question is this - what should I look for in the files
generated by lld
and gold, respectively, using  readelf?

Thanks,

Tom

  reply	other threads:[~2022-11-21 17:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-20 16:37 Tom Kacvinsky
2022-11-21 14:14 ` Nick Clifton
2022-11-21 14:51   ` Tom Kacvinsky
2022-11-21 15:16     ` Nick Clifton
2022-11-21 15:33       ` Tom Kacvinsky
2022-11-21 16:48         ` Nick Clifton
2022-11-21 17:43           ` Tom Kacvinsky [this message]
2022-11-22 11:20             ` Nick Clifton

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=CAG_eJLcYkaC_UP5YXxZF8JFnwGjC9d_SnWAfEgxMAq2rYO2KXA@mail.gmail.com \
    --to=tkacvins@gmail.com \
    --cc=binutils@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).