Path: utzoo!utgpu!attcan!uunet!cbmvax!ulowell!m2c!applix!scott
From: scott@applix.UUCP (Scott Evernden)
Newsgroups: comp.sys.amiga
Subject: Re: Dhrystone
Message-ID: <773@applix.UUCP>
Date: 10 Aug 88 05:32:13 GMT
References: <755@applix.UUCP>
Reply-To: scott@applix.UUCP (Scott Evernden)
Followup-To: comp.sys.amiga.tech
Organization: APPLiX Inc., Westboro MA
Lines: 32

In article <755@applix.UUCP> scott@applix.UUCP (Scott Evernden) writes:
> .....
>Dhrystone v2.1 results - Manx 3.6b vs Lattice 4.02
>LARGECODE & LARGEDATA 16BIT INTS:
>==================================
>lc -cw -w -v -DREG=register -Lm dhry_?.c
... etc.,

Your (my) large-model Lattice tests are hosed.
(Heady compiler junk ahead- "n" to skip...)

I just stumbled across the following facts:

o I should have remembered but forgot, that specifying -b and not specifying
  it are exactly the same.  I need to add -b0 in order to get large-data
  addressing.

o Something I didn't know: specifying -r and not specifying it are the exact
  same thing- I need to add -r0 in order to get large-code addressing.
  (apparently not in the docs; is this a secret?)

o the -Lm would _seem_ to imply that I _don't_ want SMALLCODE or SMALLDATA;
  however, the .lnk file produced by "lc" references lc.lib (the -b lib) and
  _not_ lcnb.lib (the -b0 lib) as I might have expected.  In order to
  perform a truly fair comparison, I need to explicitly modify the .lnk to
  link from the "nb" libraries.

o Having said the above, preliminary indications are that the numbers don't
  change too significantly if I do the tests properly.  If any radical
  differences appear, I will post...

-scott