From: Ian Lance Taylor <ian@cygnus.com>
To: jason@cygnus.com
Cc: robertlipe@usa.net, bfd@cygnus.com
Subject: Re: patch was: dwarf2 debug dependent upon GAS?
Date: Thu, 11 Mar 1999 18:02:00 -0000 [thread overview]
Message-ID: <199903120202.SAA25624@rtl.cygnus.com> (raw)
In-Reply-To: <u9n21jzvd5.fsf@yorick.cygnus.com>
From: Jason Merrill <jason@cygnus.com>
Date: 11 Mar 1999 11:20:22 -0800
> I assume that fixing this would dramatically improve link time for
> DWARF2?
> I would not expect to see a dramatic improvement, but maybe there is
> something I am overlooking.
I was thinking that a bunch of relocs to the same symbol would resolve
faster than relocs to different symbols; perhaps that's not the case.
No, it isn't. Each reloc contains a symbol index. When the linker
performs the relocations, it first computes a table of all the symbol
values; the linker must perform this operation anyhow in order to
generate the symbol table of the output file. Then the linker loops
through the relocs, resolving them. Calculating the value of a symbol
is just a table lookup.
Ian
prev parent reply other threads:[~1999-03-11 18:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19990226012522.D17655@rjlhome.sco.com>
[not found] ` <29507.920192219@hurl.cygnus.com>
[not found] ` <19990228160642.H20315@rjlhome.sco.com>
[not found] ` <u9u2w67y67.fsf@yorick.cygnus.com>
[not found] ` <19990301102454.Q20315@rjlhome.sco.com>
[not found] ` <u9hfs585cd.fsf@yorick.cygnus.com>
[not found] ` <19990302002736.G27552@rjlhome.sco.com>
1999-03-11 0:02 ` Jason Merrill
1999-03-11 7:41 ` Ian Lance Taylor
1999-03-11 10:31 ` Jason Merrill
1999-03-11 10:44 ` Ian Lance Taylor
1999-03-11 11:20 ` Jason Merrill
1999-03-11 18:02 ` Ian Lance Taylor [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=199903120202.SAA25624@rtl.cygnus.com \
--to=ian@cygnus.com \
--cc=bfd@cygnus.com \
--cc=jason@cygnus.com \
--cc=robertlipe@usa.net \
/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).