AuroraMiddleware/skia2
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
9fbe80777e
skia2/resources/sksl/intrinsics/DFdy.sksl

14 lines
600 B
Plaintext
Raw Normal View History

Allow derivatives in Runtime Effects when ES3 restrictions are off. We can now add functions to sksl_public.sksl with an $es3 prefix. These will be allowed in a Runtime Effect when strict-ES2 mode is disabled. Note that the CPU backend still doesn't have support for these calls, and will fail ungracefully (assertion, nonsense result) if these intrinsics are used. The testing here is limited, due to an unrelated bug in SPIR-V (skia:12340) Change-Id: I9c911bc2b77f5051e80844607e7fd08ad386ee56 Bug: skia:12202, skia:12340 Reviewed-on: https://skia-review.googlesource.com/c/skia/+/439058 Commit-Queue: John Stiles <johnstiles@google.com> Reviewed-by: Ethan Nicholas <ethannicholas@google.com>
2021-08-13 15:43:21 +00:00
uniform half4 testInputs; // equals (-1.25, 0, 0.75, 2.25)
uniform half4 colorGreen, colorRed;
half4 main(float2 coords) {
half4 expected = half4(0); // derivative of a constant is zero
return (dFdx(testInputs.x) == expected.x &&
dFdx(testInputs.xy) == expected.xy &&
dFdx(testInputs.xyz) == expected.xyz &&
Avoid mix-up between MAIN_COORDS and FRAGCOORD. When compiling test shaders, we were setting SK_FRAGCOORD_BUILTIN on the `coords` parameter to main() instead of SK_MAIN_COORDS_BUILTIN. These two built-ins don't have the same type (float2 vs. float4) and don't mean quite the same thing. The SPIR-V code generator saw a variable with the SK_FRAGCOORD_BUILTIN builtin value and assumed the presence of a global variable named `sk_FragCoord`, which didn't exist (because it was never referenced in the code, so it was never cloned in from the sksl_frag module). This is only a concern when compiling test shaders with skslc; real shaders don't hit these code paths. The generated code here is still imperfect; if you look closely, you'll see the GLSL and Metal code is referencing the `coords` variable but it's never declared anywhere. Change-Id: I3ad249469927ff35eb1e75d6536f95317502708f Bug: skia:12340 Reviewed-on: https://skia-review.googlesource.com/c/skia/+/440520 Commit-Queue: John Stiles <johnstiles@google.com> Commit-Queue: Brian Osman <brianosman@google.com> Auto-Submit: John Stiles <johnstiles@google.com> Reviewed-by: Brian Osman <brianosman@google.com>
2021-08-18 19:03:17 +00:00
dFdx(testInputs.xyzw) == expected.xyzw &&
Allow derivatives in Runtime Effects when ES3 restrictions are off. We can now add functions to sksl_public.sksl with an $es3 prefix. These will be allowed in a Runtime Effect when strict-ES2 mode is disabled. Note that the CPU backend still doesn't have support for these calls, and will fail ungracefully (assertion, nonsense result) if these intrinsics are used. The testing here is limited, due to an unrelated bug in SPIR-V (skia:12340) Change-Id: I9c911bc2b77f5051e80844607e7fd08ad386ee56 Bug: skia:12202, skia:12340 Reviewed-on: https://skia-review.googlesource.com/c/skia/+/439058 Commit-Queue: John Stiles <johnstiles@google.com> Reviewed-by: Ethan Nicholas <ethannicholas@google.com>
2021-08-13 15:43:21 +00:00
sign(dFdy(coords.xx)) == half2(0, 0) &&
sign(dFdy(coords.yy)) == half2(1, 1) &&
Avoid mix-up between MAIN_COORDS and FRAGCOORD. When compiling test shaders, we were setting SK_FRAGCOORD_BUILTIN on the `coords` parameter to main() instead of SK_MAIN_COORDS_BUILTIN. These two built-ins don't have the same type (float2 vs. float4) and don't mean quite the same thing. The SPIR-V code generator saw a variable with the SK_FRAGCOORD_BUILTIN builtin value and assumed the presence of a global variable named `sk_FragCoord`, which didn't exist (because it was never referenced in the code, so it was never cloned in from the sksl_frag module). This is only a concern when compiling test shaders with skslc; real shaders don't hit these code paths. The generated code here is still imperfect; if you look closely, you'll see the GLSL and Metal code is referencing the `coords` variable but it's never declared anywhere. Change-Id: I3ad249469927ff35eb1e75d6536f95317502708f Bug: skia:12340 Reviewed-on: https://skia-review.googlesource.com/c/skia/+/440520 Commit-Queue: John Stiles <johnstiles@google.com> Commit-Queue: Brian Osman <brianosman@google.com> Auto-Submit: John Stiles <johnstiles@google.com> Reviewed-by: Brian Osman <brianosman@google.com>
2021-08-18 19:03:17 +00:00
sign(dFdy(coords.xy)) == half2(0, 1)) ? colorGreen : colorRed;
Allow derivatives in Runtime Effects when ES3 restrictions are off. We can now add functions to sksl_public.sksl with an $es3 prefix. These will be allowed in a Runtime Effect when strict-ES2 mode is disabled. Note that the CPU backend still doesn't have support for these calls, and will fail ungracefully (assertion, nonsense result) if these intrinsics are used. The testing here is limited, due to an unrelated bug in SPIR-V (skia:12340) Change-Id: I9c911bc2b77f5051e80844607e7fd08ad386ee56 Bug: skia:12202, skia:12340 Reviewed-on: https://skia-review.googlesource.com/c/skia/+/439058 Commit-Queue: John Stiles <johnstiles@google.com> Reviewed-by: Ethan Nicholas <ethannicholas@google.com>
2021-08-13 15:43:21 +00:00
}
Reference in New Issue Copy Permalink