Timeline for Did early assembly games use hardcoded memory locations?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 9, 2017 at 8:31 | comment | added | JeremyP | The first part is not true. People often created labels for the zero page locations they used. Every 6502 assembler I ever used would check the address of the memory referencing instructions and use the zero page version automatically if possible. | |
| May 8, 2017 at 15:48 | comment | added | Tommy | Not two and three cycle, two and three byte, for three and four cycles. E.g. in the zero page case: (1) read operation; (2) read operand; (3) read from address. For an absolute read, throw in an extra cycle for reading an extra byte of address. | |
| S Jan 4, 2017 at 1:14 | history | suggested | Nisse Engström | CC BY-SA 3.0 |
Improved spelling.
|
| Jan 3, 2017 at 22:04 | review | Suggested edits | |||
| S Jan 4, 2017 at 1:14 | |||||
| Nov 2, 2016 at 1:07 | comment | added | Janka | The original Forth language for the 6502 used the zeropage as a "second stack" for the typical Forth data manipulation. It was utilizing the X register as a secondary stack pointer, which was neat because the 6502 had that (indirect,X) addressing mode, in which you could select a memory location by a pointer in the zero page given from the X register and an offset. That was a great way to use that hacky mode. | |
| Nov 2, 2016 at 0:44 | review | First posts | |||
| Nov 2, 2016 at 5:39 | |||||
| Nov 2, 2016 at 0:43 | history | answered | user3539 | CC BY-SA 3.0 |