Xref: utzoo comp.sys.ibm.pc:29016 comp.sys.amiga:34041
Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!cwjcc!neoucom!wtm
From: wtm@neoucom.UUCP (Bill Mayhew)
Newsgroups: comp.sys.ibm.pc,comp.sys.amiga
Subject: Re: OS/2 vs AmigaDOS
Summary: How about the compliers used to generate the code?
Message-ID: <1638@neoucom.UUCP>
Date: 18 May 89 13:53:10 GMT
References: <2134@iitmax.IIT.EDU> <5625@microsoft.UUCP> <5664@microsoft.UUCP> <2962@rti.UUCP>
Organization: Northeastern Ohio Universities College of Medicine
Lines: 19


The dhrystone benchmark normally doesn't make calls to
hardware-specific devices, as dhrystone is supposed to compile and
run on virtually any machine.

A 2:1 difference in the dhrystone/sec between msdos and os/2 is
suspicious.  One might want to inquire about what compilers were
used to generate the code run in the mips magazine test.  I have
seen close to 2:1 differences between Microsoft Optimizing C 5.0 and the
Green Hills or Phar-Lap compilers for msdos.  The former was emitting 16 bit
code, while the latter two were emitting 80386 code.

To the best of my knowledge, the C compiler included with os/2 developemnt
system generates only 16 bit code.

How this applies to the Amiga, I'm not sure...

Bill
wtm@impulse.UUCP