Macintosh language benchmarks
Posted: November 29th, 1984, 7:33 am
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 UW 5/3/83; site uw-beaver
Path: utzoo!watmath!clyde!burl!ulysses!cbosgd!mhuxj!houxm!hogpc!houti!ariel!vax135!cornell!uw-beaver!info-mac
From: [email protected]
Newsgroups: fa.info-mac
Subject: Macintosh language benchmarks
Message-ID:
Date: Sun, 11-Nov-84 03:13:09 EST
Article-I.D.: uw-beave.2189
Posted: Sun Nov 11 03:13:09 1984
Date-Received: Tue, 13-Nov-84 06:21:50 EST
Sender: yenbut@uw-beave
Organization: U of Washington Computer Science
Lines: 13
From:
I have been using the [notoriously awful] Whitesmith C compiler
available from "software toolworks" or some similar name. It does work,
and there are header files defining all the data structures, and
interface files so you can make all the ROM calls. I haven't found any
serious bugs, but code bloat is amazing. One reason is that Apple's
linker is a crock that doesn't have have the concept of scanning a
library! Instead it blithely loads everything contained in each library
file (which you must specify yourself -- blech!) regardless of whether
it is called for or not. Another reason for bloated code: increment a
byte in memory can be done in a single instruction, but they load the
byte into a register, extend it to a word, extend that to a long, add
one, and then store the low 8 bits of the long back into memory.
Posting-Version: version B 2.10 UW 5/3/83; site uw-beaver
Path: utzoo!watmath!clyde!burl!ulysses!cbosgd!mhuxj!houxm!hogpc!houti!ariel!vax135!cornell!uw-beaver!info-mac
From: [email protected]
Newsgroups: fa.info-mac
Subject: Macintosh language benchmarks
Message-ID:
Date: Sun, 11-Nov-84 03:13:09 EST
Article-I.D.: uw-beave.2189
Posted: Sun Nov 11 03:13:09 1984
Date-Received: Tue, 13-Nov-84 06:21:50 EST
Sender: yenbut@uw-beave
Organization: U of Washington Computer Science
Lines: 13
From:
I have been using the [notoriously awful] Whitesmith C compiler
available from "software toolworks" or some similar name. It does work,
and there are header files defining all the data structures, and
interface files so you can make all the ROM calls. I haven't found any
serious bugs, but code bloat is amazing. One reason is that Apple's
linker is a crock that doesn't have have the concept of scanning a
library! Instead it blithely loads everything contained in each library
file (which you must specify yourself -- blech!) regardless of whether
it is called for or not. Another reason for bloated code: increment a
byte in memory can be done in a single instruction, but they load the
byte into a register, extend it to a word, extend that to a long, add
one, and then store the low 8 bits of the long back into memory.