Recall Arithmetic: The haves and have-nots
|
05-24-2015, 08:40 AM
(This post was last modified: 05-24-2015 09:29 PM by PANAMATIK.)
Post: #10
|
|||
|
|||
RE: Recall Arithmetic: The haves and have-nots
(05-24-2015 01:27 AM)Paul Dale Wrote: The 25 has the opcode space for recall arithmetic. I agree. It could have been used 0x80-0x87, 0x8D-0xFD, 0x8E-0xFE, 0x8F-0xFF (05-24-2015 02:25 AM)Dave Britten Wrote: If it's an alignment issue, one has to wonder why they wouldn't have just moved other instructions around, though. Anybody have any insights into this from looking at a 25 ROM disassembly? Yes, the HP-25 disassembly shows, that the 2k ROM is fully occupied and size optimized as far as possible. The program step opcode decoding uses indirectly addressed jump tables called by the a-> rom address instruction. Code:
As an example see the jump tables located at 02000: ff. 2000: decodes 0xF0-0xFF 2020: decodes 0xE0-0xEF 2040: decodes 0xD0-0xDF As you can see the opcodes 0xED,0xEF, 0xDD-0xDF are not decoded but were used for go to destinations of other opcodes ( qenter: 1/x: ). Code:
Besides executing the recall arithmetic, there would have been needed 4 more jump tables and better decoding. I'm sure they were thinking about it and couldn't get the ROM space. Bernhard That's one small step for a man - one giant leap for mankind. |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 11 Guest(s)