From: "Zagorodnev, Grigory" <grigory.zagorodnev@intel.com>
To: "Stas Kiselev" <stas_kiselev@bk.ru>, <binutils@sources.redhat.com>
Subject: RE: Re[2]: GAS
Date: Tue, 05 Apr 2005 07:52:00 -0000 [thread overview]
Message-ID: <F92C2EFE7C3BA745855BF7036E1F3F9AADC0BB@NNSMSX401> (raw)
>The idea is: huge input file implies huge symbol tables, that results
>more hash function collisions. Thus increasing the DEFAULT_SIZE of hash
>we can reduce the number of collisions and therefore speedup execution.
>Stas, would you try this on your sources, please?
Similar issue was reported against 'ld' 1.5 years ago. Simple change of
default hash size from 4K to 64K gave 2x link time improvement.
http://lists.gnu.org/archive/html/bug-gnu-utils/2003-08/msg00153.html
Thus the patch may look like this:
$ diff gas/hash.c.org gas/hash.c
38c38
< #define DEFAULT_SIZE (4051)
---
> #define DEFAULT_SIZE (65537)
- Grigory
next reply other threads:[~2005-04-05 7:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-05 7:52 Zagorodnev, Grigory [this message]
2005-04-06 11:17 ` GAS Nick Clifton
-- strict thread matches above, loose matches on Subject: below --
2005-04-14 9:00 GAS Nick Clifton
2005-04-14 9:11 ` Re[2]: GAS Stas Kiselev
2005-04-05 5:45 Zagorodnev, Grigory
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=F92C2EFE7C3BA745855BF7036E1F3F9AADC0BB@NNSMSX401 \
--to=grigory.zagorodnev@intel.com \
--cc=binutils@sources.redhat.com \
--cc=stas_kiselev@bk.ru \
/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).