From: Ian Lance Taylor <ian@airs.com>
To: Stas Kiselev <stas_kiselev@bk.ru>
Cc: binutils@sourceware.org
Subject: Re: Optimization of GAS
Date: Fri, 01 Apr 2005 16:35:00 -0000 [thread overview]
Message-ID: <m33buaa205.fsf@gossamer.airs.com> (raw)
In-Reply-To: <E1DHOaZ-000Da8-00.stas_kiselev-bk-ru@f20.mail.ru>
Stas Kiselev <stas_kiselev@bk.ru> writes:
> I want to make GAS faster. I profiled it and found out that lots of the
> time takes on working with hash. What do you thing about changing hash
> mechanism into hash_map from stl. Will it work faster ?
STL is C++ code. gas is written in C. So using hash_map directly
would be rather difficult.
I expect that it is possible to speed up the hash code in gas. It
would also be interesting to see if it can be called less often. A
common usage is simply looking up instruction mnemonics, in which the
set of instructions is fixed at the start of assembly, and really, if
we do appropriate tests, it is fixed when the assembler is built. Can
we take advantage of that, perhaps by doing perfect hashing?
Ian
next prev parent reply other threads:[~2005-04-01 16:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-01 16:01 Stas Kiselev
2005-04-01 16:35 ` Ian Lance Taylor [this message]
2005-04-03 23:37 ` Ben Elliston
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=m33buaa205.fsf@gossamer.airs.com \
--to=ian@airs.com \
--cc=binutils@sourceware.org \
--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).