From: "Евгений Олегович" <futureboyinbox@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Ask for help with estimate of disassembly speed
Date: Thu, 12 Jul 2012 19:30:19 +0400 [thread overview]
Message-ID: <CAOpnVPnBaxixcfHd41yS2=Tbn=fPH50r3R-nbUESOfjRhct1=w@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1765 bytes --]
Hello, Dear Qemu developer!
My name is Eugene. I am a student of Mathematics and Mechanics St.
Petersburg State University Faculty.
*Why i am writing to You:*
We (our students group) need to design and develop* Disassembler, that can
parse (recognize) one **machine instruction in a minimum available clock
(tact cycle) time. *Or such Disassembler, that can parse ALL instruction
with max speed in average. In this case, Average means ratio of all
instruction to all execution time.
*Today:*
We have developed rough disassembler based on Intel encoding table (from
information in documentation volume "Instruction optimization"). And now we
need to compare speed of our disassembler with others (with Yours too). And
the second task is to simplify our model of disassembly (We consider 3
models of building Diassembler - Finite State Machine, Jump from a Table
and Block-Diagram, witch we realize with conditional crossing).
So, in our Disassembler, that we call *Speedy ( Block-Diagram was used) *-
we can simply set time counter at the begin and at the end of parsing
instruction. But we can't repeat this thing with Yours Disassembler. It
follows us ask You for help us.
*
What are we ask:*
We will be very glad and grateful, if You can send to us pure *DisAsm code
(DLL with parse function or another files)*, which speed we can measure. If
You have another materials(maybe any speed grafics, or a tests set that can
help us) or thinking of this theme - it would be very good.
What is the speed of parsing one (or more) instruction in Yours
Disassembler?
Have you made any verification tests? (Now we are developint it)
What is the metric, that You estimate the speed of Disassembler?
Thanks for reading and sorry for my mistakes,
Sincerely,
Eugene.
[-- Attachment #2: Type: text/html, Size: 4345 bytes --]
next reply other threads:[~2012-07-12 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 15:30 Евгений Олегович [this message]
2012-07-13 10:02 ` [Qemu-devel] Ask for help with estimate of disassembly speed Max Filippov
2012-07-13 10:20 ` Peter Maydell
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='CAOpnVPnBaxixcfHd41yS2=Tbn=fPH50r3R-nbUESOfjRhct1=w@mail.gmail.com' \
--to=futureboyinbox@gmail.com \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).