From: DJ Delorie <dj@redhat.com>
To: Doug Evans <dje@sebabeach.org>
Cc: fche@redhat.com, cgen@sourceware.org
Subject: Re: better use of disassembly hash table by mep port
Date: Mon, 21 Dec 2009 19:25:00 -0000 [thread overview]
Message-ID: <200912211925.nBLJPksC012648@greed.delorie.com> (raw)
In-Reply-To: <4B2DE87B.2030806@sebabeach.org> (message from Doug Evans on Sun, 20 Dec 2009 01:03:55 -0800)
> I think I understand the MEP port enough to have it starting using the
> disassembly hash table better (rather than hashing every insn to the
> same slot, blech).
MeP does that too? I mentioned m32c had that problem, and it was a
problem even with one specific ISA (the chip is weird as far as opcode
encoding goes). m32c is compounded by the explosion of opcodes caused
by the way cgen does variable-length insns.
My hash thoughts for m32c was to take each opcode, figure out which
bits are decodable for *that* opcode, and use those to put the opcode
into one or more hash entries. That allows us to use a wider set of
bits, thus fewer entries per bucket, while sidestepping the m32c's
decodable bits problem.
OTOH I've also started working on a non-cgen port of m32c.
prev parent reply other threads:[~2009-12-21 19:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-20 9:04 Doug Evans
2009-12-21 19:25 ` DJ Delorie [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=200912211925.nBLJPksC012648@greed.delorie.com \
--to=dj@redhat.com \
--cc=cgen@sourceware.org \
--cc=dje@sebabeach.org \
--cc=fche@redhat.com \
/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).