Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: Joern Rennecke <joern.rennecke@superh.com>
Cc: Joern Rennecke <amylaar@fairadsl.co.uk>, gdb-patches@sources.redhat.com
Subject: Re: [RFA (revised)] sh-sim, expand the opcode table
Date: Wed, 11 Feb 2004 19:25:00 -0000	[thread overview]
Message-ID: <402A81B9.6080009@redhat.com> (raw)
In-Reply-To: <200402111233.i1BCXF727696@linsvr1.uk.superh.com>

[-- Attachment #1: Type: text/plain, Size: 1325 bytes --]

Joern Rennecke wrote:
>>This is a multi-part message in MIME format.
>>--------------020902070606080708050409
>>Content-Type: text/plain; charset=us-ascii; format=flowed
>>Content-Transfer-Encoding: 7bit
>>
>>Hi Joern,
>>
>>Here are some benchmark results.  Following your advice, I took the
>>arith-rand test, increased its main loop count until it took around
>>10 seconds to run on my test machine, and tested it against the eight
>>optimization combinations that are tested for in the gcc torture test
>>[see methodology notes attached]
>>
>>
>>I found that my change increased the runtime by 1.5 to 2 percent
>>(even when I added the new instructions that I'm working on).
> 
> 
> Was that with or without ACE_FAST ?

Forgot to define ACE_FAST -- new results attached (just for
the 16-bit case).


>>That didn't seem too bad to me, but I took some advice from Alex
>>Oliva and tried simply changing the sh_jmp_table from char to short.
>>This much simpler change increased the runtime by only 0.5 to 1
>>percent, at the cost of 64k more data space.
> 
> 
> That makese sense... but what is the cost of adding the new instructions?

Imprecisely speaking, they did not seem to make any difference at all.
The number of new insns is actually not that great -- they only bring
the switch statement up to about 290 cases.




[-- Attachment #2: results.ace --]
[-- Type: text/plain, Size: 340 bytes --]

		orig	16bit	%inc

O0		9.048	9.049	.01
		9.050	9.035	0
O1		5.557	5.592	.63
		5.550	5.595	.81
O2		5.465	5.538	1.3
		5.460	5.535	1.4
O3		4.784	4.830	.96
		4.775	4.820	.94
O3 omit		4.695	4.747	1.1
		4.690	4.750	1.3
O3 omit unroll	4.694	4.738	.94
		4.695	4.735	.85
O3 -g		4.786	4.841	1.1
		4.780	4.840	1.3
Os		5.475	5.525	.91
		5.475	5.515	.73

  reply	other threads:[~2004-02-11 19:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-11  0:40 Michael Snyder
2004-02-11 12:33 ` Joern Rennecke
2004-02-11 19:25   ` Michael Snyder [this message]
2004-02-12 12:48     ` Joern Rennecke
2004-02-12 19:32       ` Michael Snyder

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=402A81B9.6080009@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