Path: utzoo!attcan!uunet!steinmetz!davidsen
From: davidsen@steinmetz.ge.com (William E. Davidsen Jr)
Newsgroups: comp.arch
Subject: Re: Dhrystone 2.1 discounts segment thrashing
Keywords: integer benchmark
Message-ID: <11534@steinmetz.ge.com>
Date: 15 Jul 88 12:53:06 GMT
References: <517@pcrat.UUCP> <2294@sugar.UUCP> <11722@ames.arc.nasa.gov>
Reply-To: davidsen@crdos1.UUCP (bill davidsen)
Organization: General Electric CRD, Schenectady, NY
Lines: 19

There is a common belief that something bad happens on a 286 when the
size of an array becomes greater than 64k. This is not true; it happens
when you use large or huge model. Therefore, rather than ask the
Dhrystone but modified to use other array sizes, you can just compile in
the model to be tested and get the info you want, making the 286 look as
bad as you please.

Here are some runs I made using Dhrystone 1.0 on a 286:
	value	flags
	1220	none
	1724	-Ox
	 877	-Ox -M2l

As you can see the use of large model cuts the performance in half. Why
change the benchmark when you can get the info in another way?
-- 
	bill davidsen		(wedu@ge-crd.arpa)
  {uunet | philabs | seismo}!steinmetz!crdos1!davidsen
"Stupidity, like virtue, is its own reward" -me