Changes

490 bytes added ,  21:56, 5 December 2015
m
no edit summary
Line 4: Line 4:     
The behaviour of the ifu command actually suggests 0=true and 1=false. Earlier today, upon seeing the change in the wiki, I did tests with the command. It turned out the positive block is executed when the bit is cleared, and the negative block is executed when the bit is set; as it was previously documented. Note the wording in the Shader Instruction Set page: "If condition BOOL is true, then executes instructions until DST, then jumps to DST+NUM; else, jumps to DST." --[[User:Fincs|Fincs]] 20:15, 5 December 2015 (CET)
 
The behaviour of the ifu command actually suggests 0=true and 1=false. Earlier today, upon seeing the change in the wiki, I did tests with the command. It turned out the positive block is executed when the bit is cleared, and the negative block is executed when the bit is set; as it was previously documented. Note the wording in the Shader Instruction Set page: "If condition BOOL is true, then executes instructions until DST, then jumps to DST+NUM; else, jumps to DST." --[[User:Fincs|Fincs]] 20:15, 5 December 2015 (CET)
 +
 +
: From what I've seen so far, it seems to be used with 0 = false and 1 = true, so...  ¯\_(ツ)_/¯ --[[User:Steveice10|Steveice10]] 20:18, 5 December 2015 (CET)
 +
 +
:: Could you elaborate? --[[User:Neobrain|Neobrain]] 20:20, 5 December 2015 (CET)
 +
 +
::: As in, disassembled code I've looked at seems to use 0 for false and 1 for true when changing the register value. Plus, the register bits are specifically initialized to zeros. --[[User:Steveice10|Steveice10]] 20:56, 5 December 2015 (CET)
1,434

edits