Talk:GPU/Internal Registers - Revision history

Steveice10 at 19:56, 5 December 2015

2015-12-05T18:56:58Z

← Older revision		Revision as of 21:56, 5 December 2015
Line 8:		Line 8:

	:: Could you elaborate? --[[User:Neobrain\|Neobrain]] 20:20, 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)

Neobrain at 19:20, 5 December 2015

2015-12-05T18:20:39Z

← Older revision		Revision as of 21:20, 5 December 2015
Line 6:		Line 6:

	: 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)		: 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)

Steveice10 at 19:18, 5 December 2015

2015-12-05T18:18:45Z

← Older revision		Revision as of 21:18, 5 December 2015
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)

Fincs at 19:15, 5 December 2015

2015-12-05T18:15:42Z

← Older revision		Revision as of 21:15, 5 December 2015
Line 2:		Line 2:

	@Steveice: <s>Regarding the recent GPUREG_SH_BOOLUNIFORM confusion, I agree that your version is the more sensible variant. However, note that technically it depends on the semantics defined in [[Shader_Instruction_Set#Comparison_operator]]: Switching between your version (0=false) and the original one (1=false) is equivalent to e.g. replacing the CONDOP=0 semantic " cmp.x == REFX \|\| cmp.y == REFY " with " !cmp.x == REFX \|\| !cmp.y == REFY". In other words, this change implicltly changed the documented semantics of shader conditions. Hence I wonder whether the Shader Instruction Set needs any adjustments with the new documentation on GPUREG_SH_BOOLUNIFORM. </s> Actually, I mixed up stuff. What actually would need to be fixed up is the semantics of IFU, but that would yield a counterintuitive notion of conditional execution. [[User:Neobrain\|Neobrain]] 19:55, 5 December 2015 (CET)		@Steveice: <s>Regarding the recent GPUREG_SH_BOOLUNIFORM confusion, I agree that your version is the more sensible variant. However, note that technically it depends on the semantics defined in [[Shader_Instruction_Set#Comparison_operator]]: Switching between your version (0=false) and the original one (1=false) is equivalent to e.g. replacing the CONDOP=0 semantic " cmp.x == REFX \|\| cmp.y == REFY " with " !cmp.x == REFX \|\| !cmp.y == REFY". In other words, this change implicltly changed the documented semantics of shader conditions. Hence I wonder whether the Shader Instruction Set needs any adjustments with the new documentation on GPUREG_SH_BOOLUNIFORM. </s> Actually, I mixed up stuff. What actually would need to be fixed up is the semantics of IFU, but that would yield a counterintuitive notion of conditional execution. [[User:Neobrain\|Neobrain]] 19:55, 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)

Neobrain at 19:14, 5 December 2015

2015-12-05T18:14:38Z

← Older revision		Revision as of 21:14, 5 December 2015
Line 1:		Line 1:
	<s>FYI, fixed-point numbers are often denoted as "fixedX.Y", with X the non-fractional and Y the fractional bits. Also note that one wouldn't speak about "fixed-point" numbers when Y=0 (just say "X-bit integer" instead). I found the latter a bit confusing in the recent changes, since it sounded like "Z bias" was a fixed-point number with unspecified fractional bits. [[User:Neobrain\|Neobrain]] 12:07, 3 December 2015 (CET)</s>		<s>FYI, fixed-point numbers are often denoted as "fixedX.Y", with X the non-fractional and Y the fractional bits. Also note that one wouldn't speak about "fixed-point" numbers when Y=0 (just say "X-bit integer" instead). I found the latter a bit confusing in the recent changes, since it sounded like "Z bias" was a fixed-point number with unspecified fractional bits. [[User:Neobrain\|Neobrain]] 12:07, 3 December 2015 (CET)</s>

	@Steveice: Regarding the recent GPUREG_SH_BOOLUNIFORM confusion, I agree that your version is the more sensible variant. However, note that technically it depends on the semantics defined in [[Shader_Instruction_Set#Comparison_operator]]: Switching between your version (0=false) and the original one (1=false) is equivalent to e.g. replacing the CONDOP=0 semantic " cmp.x == REFX \|\| cmp.y == REFY " with " !cmp.x == REFX \|\| !cmp.y == REFY". In other words, this change implicltly changed the documented semantics of shader conditions. Hence I wonder whether the Shader Instruction Set needs any adjustments with the new documentation on GPUREG_SH_BOOLUNIFORM. [[User:Neobrain\|Neobrain]] 19:55, 5 December 2015 (CET)		@Steveice: <s>Regarding the recent GPUREG_SH_BOOLUNIFORM confusion, I agree that your version is the more sensible variant. However, note that technically it depends on the semantics defined in [[Shader_Instruction_Set#Comparison_operator]]: Switching between your version (0=false) and the original one (1=false) is equivalent to e.g. replacing the CONDOP=0 semantic " cmp.x == REFX \|\| cmp.y == REFY " with " !cmp.x == REFX \|\| !cmp.y == REFY". In other words, this change implicltly changed the documented semantics of shader conditions. Hence I wonder whether the Shader Instruction Set needs any adjustments with the new documentation on GPUREG_SH_BOOLUNIFORM. </s> Actually, I mixed up stuff. What actually would need to be fixed up is the semantics of IFU, but that would yield a counterintuitive notion of conditional execution. [[User:Neobrain\|Neobrain]] 19:55, 5 December 2015 (CET)

Neobrain at 18:55, 5 December 2015

2015-12-05T17:55:31Z

← Older revision		Revision as of 20:55, 5 December 2015
Line 1:		Line 1:
	<s>FYI, fixed-point numbers are often denoted as "fixedX.Y", with X the non-fractional and Y the fractional bits. Also note that one wouldn't speak about "fixed-point" numbers when Y=0 (just say "X-bit integer" instead). I found the latter a bit confusing in the recent changes, since it sounded like "Z bias" was a fixed-point number with unspecified fractional bits. [[User:Neobrain\|Neobrain]] 12:07, 3 December 2015 (CET)</s>		<s>FYI, fixed-point numbers are often denoted as "fixedX.Y", with X the non-fractional and Y the fractional bits. Also note that one wouldn't speak about "fixed-point" numbers when Y=0 (just say "X-bit integer" instead). I found the latter a bit confusing in the recent changes, since it sounded like "Z bias" was a fixed-point number with unspecified fractional bits. [[User:Neobrain\|Neobrain]] 12:07, 3 December 2015 (CET)</s>

			@Steveice: Regarding the recent GPUREG_SH_BOOLUNIFORM confusion, I agree that your version is the more sensible variant. However, note that technically it depends on the semantics defined in [[Shader_Instruction_Set#Comparison_operator]]: Switching between your version (0=false) and the original one (1=false) is equivalent to e.g. replacing the CONDOP=0 semantic " cmp.x == REFX \|\| cmp.y == REFY " with " !cmp.x == REFX \|\| !cmp.y == REFY". In other words, this change implicltly changed the documented semantics of shader conditions. Hence I wonder whether the Shader Instruction Set needs any adjustments with the new documentation on GPUREG_SH_BOOLUNIFORM. [[User:Neobrain\|Neobrain]] 19:55, 5 December 2015 (CET)

Neobrain at 11:04, 4 December 2015

2015-12-04T10:04:47Z

← Older revision		Revision as of 13:04, 4 December 2015
Line 1:		Line 1:
	FYI, fixed-point numbers are often denoted as "fixedX.Y", with X the non-fractional and Y the fractional bits. Also note that one wouldn't speak about "fixed-point" numbers when Y=0 (just say "X-bit integer" instead). I found the latter a bit confusing in the recent changes, since it sounded like "Z bias" was a fixed-point number with unspecified fractional bits. [[User:Neobrain\|Neobrain]] 12:07, 3 December 2015 (CET)		<s>FYI, fixed-point numbers are often denoted as "fixedX.Y", with X the non-fractional and Y the fractional bits. Also note that one wouldn't speak about "fixed-point" numbers when Y=0 (just say "X-bit integer" instead). I found the latter a bit confusing in the recent changes, since it sounded like "Z bias" was a fixed-point number with unspecified fractional bits. [[User:Neobrain\|Neobrain]] 12:07, 3 December 2015 (CET)</s>

Neobrain at 11:08, 3 December 2015

2015-12-03T10:08:54Z

← Older revision		Revision as of 13:08, 3 December 2015
Line 1:		Line 1:
	FYI, fixed-point numbers are often denoted as "fixedX.Y", with X the non-fractional and Y the fractional bits. Also note that one wouldn't speak about "fixed-point" numbers when Y=0 (just say "X-bit integer" instead). [[User:Neobrain\|Neobrain]] 12:07, 3 December 2015 (CET)		FYI, fixed-point numbers are often denoted as "fixedX.Y", with X the non-fractional and Y the fractional bits. Also note that one wouldn't speak about "fixed-point" numbers when Y=0 (just say "X-bit integer" instead). I found the latter a bit confusing in the recent changes, since it sounded like "Z bias" was a fixed-point number with unspecified fractional bits. [[User:Neobrain\|Neobrain]] 12:07, 3 December 2015 (CET)

Neobrain: Created page with "FYI, fixed-point numbers are often denoted as "fixedX.Y", with X the non-fractional and Y the fractional bits. Also note that one wouldn't speak about "fixed-point" numbers when ..."

2015-12-03T10:07:52Z

Created page with "FYI, fixed-point numbers are often denoted as "fixedX.Y", with X the non-fractional and Y the fractional bits. Also note that one wouldn't speak about "fixed-point" numbers when ..."

New page

FYI, fixed-point numbers are often denoted as "fixedX.Y", with X the non-fractional and Y the fractional bits. Also note that one wouldn't speak about "fixed-point" numbers when Y=0 (just say "X-bit integer" instead). [[User:Neobrain|Neobrain]] 12:07, 3 December 2015 (CET)