Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!ames!ptsfa!ihnp4!homxb!mtuxo!mtune!codas!ge-dab!ge-rtp!edison!toylnd!dca
From: dca@toylnd.UUCP (David C. Albrecht)
Newsgroups: comp.sys.amiga
Subject: Re: AllocMem() with 16-bit Manx
Message-ID: <174@toylnd.UUCP>
Date: Sun, 20-Sep-87 15:17:54 EDT
Article-I.D.: toylnd.174
Posted: Sun Sep 20 15:17:54 1987
Date-Received: Thu, 24-Sep-87 05:12:00 EDT
References: <8709141841.AA06918@cory.Berkeley.EDU> <1584@gryphon.CTS.COM>
Organization: Dave & Anne in Charlottesville, VA
Lines: 25

> >	I would suggest Aztec-C mainly because it will compile int's as either
> >16 bits or 32 bits (Most Atari compilers use 16 bit ints), and you don't want
> >to have to worry about a program compilable under BOTH 16 and 32 bit ints.
> >
> So does Lattice these days. 3.10 handles 16 bit or 32 bit integers nicely.

Weeell, first off let me say that I use Lattice because when I was starting
off I was more interested in speed of implementation than speed of result and
Manx in 16 bit mode has some real negative aspects in this regard.  There is
a difference between saying 16 bit 'ints' and 16 bit 'shorts'.  As far as I
know of Lattice 3.10 doesn't support 16 bit 'ints'.  In any case, when it
comes to using 16 bit ints in Lattice though I have to differ, they don't
handle them very nicely.  Case in point:  I noticed that some of the dhrystone
results reported for the Amiga and the ST were reported for 16 bit ints.
I decided I would see how well Lattice would perform if I went through and
changed all the various 'int' declarations to 'short' and then compiled under
Lattice.  It made virtually no difference the results were still under 700
dhrystones unlike Manx which gives in the 900 territory.  Note that I had
already tried this experiment on my AT&T Unix PC which is based on a 10Mhz
68010 and a compiler that uses 32 bit ints and it went from about 1050
dhrystones to over 1300.  Needless to say I was a bit disapointed by Lattice's
performance.  Hopefully the as yet vaporware 4.0 version will correct
the situation.

David Albrecht