z80 timing... 6502 timing

From: Richard Erlacher <edick_at_idcomm.com>
Date: Sat Apr 17 16:21:34 1999

Well, you'd have to be careful to avoid mixing up the timing in the system
intrinsics to be "postulated" and the contest-specific code. How would that
be handled?

Dick

-----Original Message-----
From: Sean 'Captain Napalm' Conner <spc_at_armigeron.com>
To: Discussion re-collecting of classic computers
<classiccmp_at_u.washington.edu>
Date: Saturday, April 17, 1999 3:14 PM
Subject: Re: z80 timing... 6502 timing


>It was thus said that the Great Mike Ford once stated:
>>
>> >Ooh! A machine code competition. I'm in! I'll do the 6502 and whoop
>> >EVERYONE'S ass!
>>
>> And then you woke up. First what are the rules, 6502 or 65C02, code in
Rom
>> or Ram, what is the code supposed to do?
>>
>> My vote goes for something with some graphical element so we can "see"
what
>> is happening. (spinning ball, etc.)
>
> I would vote against that because the hardware available might make a
>difference. For instance, moving an object on a 6502 based system, the
C-64
>will probably win both the speed and size catagories, simply because of
>hardware assist. Besides, if this is to match code/speed size between
CPUs,
>then not all machines are capable of graphics.
>
> The Roman Numeral one sounds interesting. To make it fair, I would
assume
>that there exists a routine, CHROUT, that takes as input the character in
>the main accumulator and displays it on the output device. The output
>device is a simple TTY like device that supports TAB, CR (which returns the
>print head to the start of the line, and advances to the next line) and BS.
>
> The code for CHROUT is NOT to be counted towards speed or size, but I'd
>probably allow the call to CHROUT to be considered.
>
> Contest open for any CPU anyone would care to write code for.
>
> -spc (Hows that for a contest?)
>
Received on Sat Apr 17 1999 - 16:21:34 BST