Jump - Revision history

Mr z: Protected "Jump" ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))

2010-12-04T08:45:28Z

Protected "Jump" ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))

Mr z at 07:59, 7 October 2007

2007-10-07T07:59:11Z

Mr z at 07:56, 7 October 2007

2007-10-07T07:56:50Z

Mr z: Add note about "CALL"

2007-10-07T07:47:27Z

Add note about "CALL"

Mr z at 16:06, 18 January 2005

2005-01-18T16:06:54Z

Pingaso at 17:11, 17 January 2005

2005-01-17T17:11:15Z

Pingaso at 01:15, 12 January 2005

2005-01-12T01:15:04Z

Pingaso at 21:30, 11 January 2005

2005-01-11T21:30:48Z

Pingaso at 21:22, 11 January 2005

2005-01-11T21:22:20Z

Pingaso at 20:38, 11 January 2005

2005-01-11T20:38:14Z

@@ Line 33: / Line 33: @@
 Note that if the return address is stored in a register, the address stored in that register is the address that is exactly 3 addresses after the start of the Jump opcode, so that the subroutine will return to the next opcode after the Jump opcode.  Some routines use the fact that R4 and R5 are incrementing counters, and so will place data after the Jump instruction.  See [[Calling Conventions]] for more details on function calls.<br/>
-The Jump opcode is often represented as many different mnemonics, to make life a little easier for the programmer.  The mnemonic used to represent this opcode depends on the combination of the rr and ff parameters mentioned above, according to the following charts.  Also note that <TT>CALL <I>label</I></TT> is an alias for <TT>JSR R5, <I>label</I></TT>.<br/><br/>
+The Jump opcode is often represented as many different mnemonics, to make life a little easier for the programmer.  The mnemonic used to represent this opcode depends on the combination of the rr and ff parameters mentioned above, according to the following charts.  Also, the instruction <TT>CALL <I>label</I></TT> is an alias for <TT>JSR R5, <I>label</I></TT>.<br/><br/>
 <strong>Mnemonics To Parameters</strong><br/>

@@ Line 2: / Line 2: @@
 <table border>
 <tr><td>Instruction Name</td><td>Jump</td></tr>
-<tr><td>Mnemonics</td><td>J/JE/JD/JSR/JSRE/JSRD</td></tr>
+<tr><td>Mnemonics</td><td>J/JE/JD/JSR/JSRE/JSRD/CALL</td></tr>
 <tr><td>CP1610 Clock Cycles</td><td>12</td></tr>
 <tr><td>Interruptible</td><td>Yes</td></tr>
@@ Line 33: / Line 33: @@
 Note that if the return address is stored in a register, the address stored in that register is the address that is exactly 3 addresses after the start of the Jump opcode, so that the subroutine will return to the next opcode after the Jump opcode.  Some routines use the fact that R4 and R5 are incrementing counters, and so will place data after the Jump instruction.  See [[Calling Conventions]] for more details on function calls.<br/>
-The Jump opcode is often represented as many different mnemonics, to make life a little easier for the programmer.  The mnemonic used to represent this opcode depends on the combination of the rr and ff parameters mentioned above, according to the following charts.  Also note that <TT>CALL <I>label</I><TT> is an alias for <TT>JSR R5, <I>label</I></TT>.<br/><br/>
+The Jump opcode is often represented as many different mnemonics, to make life a little easier for the programmer.  The mnemonic used to represent this opcode depends on the combination of the rr and ff parameters mentioned above, according to the following charts.  Also note that <TT>CALL <I>label</I></TT> is an alias for <TT>JSR R5, <I>label</I></TT>.<br/><br/>
 <strong>Mnemonics To Parameters</strong><br/>

@@ Line 33: / Line 33: @@
 Note that if the return address is stored in a register, the address stored in that register is the address that is exactly 3 addresses after the start of the Jump opcode, so that the subroutine will return to the next opcode after the Jump opcode.  Some routines use the fact that R4 and R5 are incrementing counters, and so will place data after the Jump instruction.  See [[Calling Conventions]] for more details on function calls.<br/>
-The Jump opcode is often represented as many different mnemonics, to make life a little easier for the programmer.  The mnemonic used to represent this opcode depends on the combination of the rr and ff parameters mentioned above, according to the following charts.<br/><br/>
+The Jump opcode is often represented as many different mnemonics, to make life a little easier for the programmer.  The mnemonic used to represent this opcode depends on the combination of the rr and ff parameters mentioned above, according to the following charts.  Also note that <TT>CALL <I>label</I><TT> is an alias for <TT>JSR R5, <I>label</I></TT>.<br/><br/>
 <strong>Mnemonics To Parameters</strong><br/>

@@ Line 31: / Line 31: @@
          aaaaaaaaaaaaaaaa    indicates the address to where the [[CP1610]] should Jump
-Note that if the return address is stored in a register, the address stored in that register is the address that is exactly 3 addresses after the start of the Jump opcode, so that the subroutine will return to the next opcode after the Jump opcode.<br/>
+Note that if the return address is stored in a register, the address stored in that register is the address that is exactly 3 addresses after the start of the Jump opcode, so that the subroutine will return to the next opcode after the Jump opcode.  Some routines use the fact that R4 and R5 are incrementing counters, and so will place data after the Jump instruction.  See [[Calling Conventions]] for more details on function calls.<br/>
 The Jump opcode is often represented as many different mnemonics, to make life a little easier for the programmer.  The mnemonic used to represent this opcode depends on the combination of the rr and ff parameters mentioned above, according to the following charts.<br/><br/>

@@ Line 6: / Line 6: @@
 <tr><td>Interruptible</td><td>Yes</td></tr>
 <tr><td>Opcode Range</td><td>$0004</td></tr>
 </table><br/>

← Older revision	Revision as of 08:45, 4 December 2010
(No difference)

@@ Line 10: / Line 10: @@
 Jump is a family of three-decle instructions that all map to the $0004 opcode and are represented as any of several different possible mnemonics, depending on the flags indicated in the second decle of the opcode.  The opcode format breaks down as follows.
-     Format - Decle #1     Format - Decle #2     Format - Decle #3
+     Format - Decle #1    Format - Decle #2    Format - Decle #3
 :0000:0000:0100  0000:00rr:aaaa:aaff  0000:00aa:aaaa:aaaa<br/>
      where:<br/>

← Older revision		Revision as of 21:22, 11 January 2005
Line 1:		Line 1:
	[[Category:CP1610]]		[[Category:CP1610]]
		+	<table border>
		+	<tr><td>Instruction Name</td><td>Jump</td></tr>
		+	<tr><td>Mnemonics</td><td>J/JE/JD/JSR/JSRE/JSRD</td></tr>
		+	<tr><td>CP1610 Clock Cycles</td><td>12</td></tr>
		+	<tr><td>Interruptible</td><td>Yes</td></tr>
		+	<tr><td>Opcode Range</td><td>$0004</td></tr>
		+	</table><br/>
		+
	Jump is a three-decle opcode that is represented as one of several different possible mnemonics, depending on the flags indicated in the second decle of the opcode. The opcode breaks down as follows.		Jump is a three-decle opcode that is represented as one of several different possible mnemonics, depending on the flags indicated in the second decle of the opcode. The opcode breaks down as follows.

@@ Line 24: / Line 24: @@
 The Jump opcode is often represented as many different mnemonics, to make life a little easier for the programmer.  The mnemonic used to represent this opcode depends on the combination of the rr and ff parameters mentioned above, according to the following charts.<br/><br/>
-<strong>Mnemonics From Parameters</strong><br/>
+<strong>Mnemonics To Parameters</strong><br/>
 <table border>
 <tr><th>Mnemonic</th><th>rr</th><th>ff</th></tr>
@@ Line 36: / Line 36: @@
 </table><br/>
-<strong>Parameters From Mnemonics</strong><br/>
+<strong>Parameters To Mnemonics</strong><br/>
 <table border>
 <tr><td></td><td>rr == 00</td><td>rr == 01</td><td>rr == 10</td><td>rr == 11</td></tr>