User Tools

Site Tools


base:kernal_floating_point_mathematics

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
base:kernal_floating_point_mathematics [2019-10-14 10:07] – [2.4 Division] silverdrbase:kernal_floating_point_mathematics [2020-12-06 20:22] – [7.3 Integer to FP], Lothar Englisch says $bc3c converts a signed 8-bit value. pararaum
Line 234: Line 234:
 **$bc44** = Convert signed 16-bit integer held in FAC1 at $63 (lo) and $62 (high) to FP\\ **$bc44** = Convert signed 16-bit integer held in FAC1 at $63 (lo) and $62 (high) to FP\\
 **$b391** = Convert signed 16-bit integer held in Y/A (lo/high) to a FP number in FAC1\\ **$b391** = Convert signed 16-bit integer held in Y/A (lo/high) to a FP number in FAC1\\
-**$bc3c** = Convert unsigned 8-bit integer held in A to a FP number in FAC1\\+**$bc3c** = Convert signed 8-bit integer held in A to a FP number in FAC1\\
 **$b3a2** = Convert unsigned 8-bit integer held in Y to a FP number in FAC1 **$b3a2** = Convert unsigned 8-bit integer held in Y to a FP number in FAC1
  
 The first routine is the actual code. The other entries simply set up $62/$63 for you. This routine wrecks FAC2, so if it is needed, it should be loaded after the conversion. It also uselessly (from our ML standpoint) sets the data type flag at $0d. Skipping these routines and jumping straight to the normalization routine at **$b8d2** gives greater control, i.e. 24-bit and 32-bit integer inputs are possible, as are signed 8-bit inputs. For example, to convert a 24-bit number, load FAC1 with the number from the most-significant byte to the least. Store zero in the last mantissa byte, and also in the sign and rounding bytes ($66 and $70). Then set the exponent to 24 (24 + $80 = $98). Jump to $b8d2 with the carry indicating whether the result should be positive (set) or negative (clear).  The first routine is the actual code. The other entries simply set up $62/$63 for you. This routine wrecks FAC2, so if it is needed, it should be loaded after the conversion. It also uselessly (from our ML standpoint) sets the data type flag at $0d. Skipping these routines and jumping straight to the normalization routine at **$b8d2** gives greater control, i.e. 24-bit and 32-bit integer inputs are possible, as are signed 8-bit inputs. For example, to convert a 24-bit number, load FAC1 with the number from the most-significant byte to the least. Store zero in the last mantissa byte, and also in the sign and rounding bytes ($66 and $70). Then set the exponent to 24 (24 + $80 = $98). Jump to $b8d2 with the carry indicating whether the result should be positive (set) or negative (clear). 
  
-The above process is basically what the KERNAL authors did to implement the 24 bit TI variable in BASIC (though they zero the high byte instead of the low, and hence use a mantissa of $a0).+The above process is basically what the KERNAL authors did to implement the 24 bit TI variable in BASIC (though they zero the high byte instead of the low, and hence use an exponent of $a0).
  
 You can take advantage of their work with the following pair of calls to convert a 24 bit unsigned integer held in YXA: You can take advantage of their work with the following pair of calls to convert a 24 bit unsigned integer held in YXA:
base/kernal_floating_point_mathematics.txt · Last modified: 2020-12-06 20:48 by pararaum