From: Michael Snyder <msnyder@redhat.com>
To: Joern Rennecke <amylaar@fairadsl.co.uk>
Cc: joern.rennecke@superh.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] sh-sim: free up some room in jump_table
Date: Mon, 09 Feb 2004 20:34:00 -0000 [thread overview]
Message-ID: <4027EED0.9050608@redhat.com> (raw)
In-Reply-To: <200402071831.i17IVRLD001695@meolyon.local>
Joern Rennecke wrote:
>>! printf (" if (target_dsp && \n");
>>! printf (" (iword & 0xf000) == 0xf000)\n");
>>! printf (" switch (sh_dsp_table[iword & 0xfff]) {\n");
>> gensim_caselist (movsxy_tab);
>>! printf (" else switch (jump_table[iword]) {\n");
>
>
> You have changed a straight dispatch into an if-then-else with
> two dispatches, and the integer and fpu arithmetic path goes the long way
> round the dsp dispatch; this seems to be a surefire way to make the
> simulator slower.
>
> We don't relly care much about the total size of the simulator, but
> we care about its working set size, so why don't you generate two
> separate simulator main loops, to be compiler into separate *.o
> files, one with the FPU instructions, and the other one with the
> dsp instructions?
OK, I need to catch up with you here. So, your concern is not
with the time it takes to execute the if condition, but with the
size and/or distribution of the working set? I'm not very used
to programming around such considerations, so I'll look to you
for guidance.
I can see the sense of making two loops, but why would it
be necessary for them to be in two separate compilation units?
Would you be willing to specify a performance test that I can
use, and a test criterion for me to meet? It might save time,
given that we seem to have a 24 hour email cycle.
next prev parent reply other threads:[~2004-02-09 20:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-07 0:29 Michael Snyder
2004-02-07 18:25 ` Joern Rennecke
2004-02-09 20:34 ` Michael Snyder [this message]
2004-02-09 20:38 ` Joern Rennecke
2004-02-09 21:16 ` Joern Rennecke
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=4027EED0.9050608@redhat.com \
--to=msnyder@redhat.com \
--cc=amylaar@fairadsl.co.uk \
--cc=gdb-patches@sources.redhat.com \
--cc=joern.rennecke@superh.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