glslang/Test/hlsl.type.half.frag


float4 main() : SV_Target0
{
    half  h0 = 0;
    half1 h1 = 1;
    half2 h2 = 2;
    half3 h3 = 3;
    half4 h4 = 4;

    half1x1 h11;
    half1x2 h12;
    half1x3 h13;
    half1x4 h14;
    half2x1 h21;
    half2x2 h22 = half2x2(1,2,3,4);
    half2x3 h23 = (half2x3)4.9;
    half2x4 h24;
    half3x1 h31;
    half3x2 h32;
    half3x3 h33;
    half3x4 h34;
    half4x1 h41;
    half4x2 h42;
    half4x3 h43;
    half4x4 h44;

    return h23._11 + h4.y + h0;
}
HLSL: allow scalar type keywords as identifiers, and add half type support. HLSL allows type keywords to also be identifiers, so a sequence such as "float half = 3" is valid, or more bizzarely, something like "float.float = int.uint + bool;" There are places this is not supported. E.g, it's permitted for struct members, but not struct names or functions. Also, vector or matrix types such as "float3" are not permitted as identifiers. This PR adds that support, as well as support for the "half" type. In production shaders, this was seen with variables named "half". The PR attempts to support this without breaking useful grammar errors such as "; expected" at the end of unterminated statements, so it errs on that side at the possible expense of failing to accept valid constructs containing a type keyword identifier. If others are discovered, they can be added. Also, half is now accepted as a valid type, alongside the min*float types. 2016-12-27 01:45:52 +00:00
			`float4 main() : SV_Target0`
			`{`
			`half h0 = 0;`
			`half1 h1 = 1;`
			`half2 h2 = 2;`
			`half3 h3 = 3;`
			`half4 h4 = 4;`

HLSL: Implement half matrices, and map all half* -> float*. 2017-06-07 05:35:25 +00:00			`half1x1 h11;`
			`half1x2 h12;`
			`half1x3 h13;`
			`half1x4 h14;`
			`half2x1 h21;`
			`half2x2 h22 = half2x2(1,2,3,4);`
			`half2x3 h23 = (half2x3)4.9;`
			`half2x4 h24;`
			`half3x1 h31;`
			`half3x2 h32;`
			`half3x3 h33;`
			`half3x4 h34;`
			`half4x1 h41;`
			`half4x2 h42;`
			`half4x3 h43;`
			`half4x4 h44;`

			`return h23._11 + h4.y + h0;`
HLSL: allow scalar type keywords as identifiers, and add half type support. HLSL allows type keywords to also be identifiers, so a sequence such as "float half = 3" is valid, or more bizzarely, something like "float.float = int.uint + bool;" There are places this is not supported. E.g, it's permitted for struct members, but not struct names or functions. Also, vector or matrix types such as "float3" are not permitted as identifiers. This PR adds that support, as well as support for the "half" type. In production shaders, this was seen with variables named "half". The PR attempts to support this without breaking useful grammar errors such as "; expected" at the end of unterminated statements, so it errs on that side at the possible expense of failing to accept valid constructs containing a type keyword identifier. If others are discovered, they can be added. Also, half is now accepted as a valid type, alongside the min*float types. 2016-12-27 01:45:52 +00:00			`}`