Post Reply 
HP-41 Byte Table
12-27-2018, 09:18 PM
Post: #6
RE: HP-41 Byte Table
They don't carry the same jump distance. That low nybble of the opcode is part of the offset!

If you construct a GTO or XEQ with an incorrect offset, the instruction will jump to an incorrect location, and undesired behavior will most likely result. You should construct your GTO and XEQ instructions with their offsets set to zero, and let the calculator find the label and calculate the offset when it first executes the code.

(I guess you do want pre-compiled offsets when you're generating code for use in ROMs, but I've never dealt with that.)
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
HP-41 Byte Table - JurgenRo - 12-27-2018, 07:54 PM
RE: HP-41 Byte Table - Thomas Okken - 12-27-2018, 08:31 PM
RE: HP-41 Byte Table - JurgenRo - 12-27-2018, 09:05 PM
RE: HP-41 Byte Table - JurgenRo - 12-27-2018, 09:11 PM
RE: HP-41 Byte Table - Sylvain Cote - 12-28-2018, 04:43 PM
RE: HP-41 Byte Table - JurgenRo - 12-28-2018, 08:34 PM
RE: HP-41 Byte Table - Sylvain Cote - 12-27-2018, 09:02 PM
RE: HP-41 Byte Table - JurgenRo - 12-27-2018, 10:46 PM
RE: HP-41 Byte Table - Thomas Okken - 12-27-2018 09:18 PM
RE: HP-41 Byte Table - JurgenRo - 12-27-2018, 09:22 PM
RE: HP-41 Byte Table - hth - 12-28-2018, 05:14 PM
RE: HP-41 Byte Table - JurgenRo - 12-28-2018, 08:44 PM
RE: HP-41 Byte Table - Sylvain Cote - 12-28-2018, 09:17 PM
RE: HP-41 Byte Table - Thomas Okken - 12-28-2018, 11:44 PM
RE: HP-41 Byte Table - JurgenRo - 12-28-2018, 11:57 PM



User(s) browsing this thread: 1 Guest(s)