Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!husc6!m2c!wpi!greyelf From: greyelf@wpi.wpi.edu (Michael J Pender) Newsgroups: comp.sys.apple Subject: Re: C on the apple Message-ID: <7604@wpi.wpi.edu> Date: 2 Feb 90 23:08:00 GMT References: <6695@wpi.wpi.edu> <12647@cbnewsd.ATT.COM> <6761@wpi.wpi.edu> <10381@microsoft.UUCP> <12046@smoke.BRL.MIL> <17437@athertn.Atherton.COM> <12054@smoke.BRL.MIL> <996@rbdc.UUCP> Reply-To: greyelf@wpi.wpi.edu (Michael J Pender) Organization: Worcester Polytechnic Institute, Worcester ,MA Lines: 33 In article <996@rbdc.UUCP> mitch@rbdc.UUCP (Mitch Berry) writes: >In article <12054@smoke.BRL.MIL> gwyn@brl.arpa (Doug Gwyn) writes: >>activation record. The 6502 hardware stack is too small for serious >>C applications even if it were used only to hold return addresses. > >What about the 65c02? or is it just a slightly souped up 6502b...i dont >know about many of the differences of the 6502 & 65c02.... The 65c02 wouldn't really help. The additional instructions of the 65c02 are mostly concerned with a new addressing mode, a short range absolute branch, instructions to push and pop x and y on and off the stack, an instruction to store zeroes in memory, and the test and set bits and test and reset bits instructions. They make some common operations faster. On the other hand, the 65c802 would be well suited to the task. It is pin-compatible with the 6502 and 65c02, and has a stack pointer and fast access pointer. The stack could be made very large by simply testing the stack pointer, and when it reaches a given value, incrementing the stack page pointer. This would allow a real dynamic stack that could grow and shrink. The 6502 and 65c02 are fast for zero page addresses. The fast access pointer allows fast access instructions to be set to access any page. --- Michael J Pender Jr Box 1942 c/o W.P.I. ... (Mankind) has already greyelf@wpi.bitnet 100 Institute Rd. used its last chance. greyelf@wpi.wpi.edu Worcester, Ma 01609 - Gen. MacArthur