GLSL bug: strange name collision between global and inout parameter
Reported by
fabrice....@gmail.com,
Dec 5 2017
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36 Example URL: https://www.shadertoy.com/view/4llBR2 Steps to reproduce the problem: make a glsl program containing: vec3 p; void G (inout vec3 q) { } void F(vec3 p) { G(p); } What is the expected behavior? compile What went wrong? doesn't compile on linux, while compile on windows. Unknown error "error C7565: assignment to varying". compiles if - change name for one of the p - suppress inout - call G(p) directly in main Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? N/A Chrome version: 62.0.3202.94 Channel: stable OS Version: 14.04 Flash Version: Shockwave Flash 27.0 r0 acid test obtained from the complex case https://www.shadertoy.com/view/MsXfzj May somebody please set the tags Blink>WebGL , Internals>GPU ? thanks !
,
Dec 6 2017
,
Dec 6 2017
CC'ing Olli in case he has the cycles to look at this.
,
Dec 7 2017
This might be an issue in the GPU driver. Which GPU was this seen on? Probably possible to work around.
,
Dec 7 2017
nVidias : GTX 760 , K2100M , and some others. possible driver bug: workaround is useful, but telling driver's people would also be good ;-)
,
Dec 7 2017
Repros for me, seems NVIDIA specific
,
Dec 19 2017
A fix will be coming in a future NVIDIA driver update. Here's a conformance test covering the issue: https://github.com/KhronosGroup/WebGL/pull/2565 Still considering a workaround as well.
,
Jan 2 2018
The fix for this bug will be released in a future NVIDIA driver update (likely version 39*). Workaround would be a bit complex, and the impact of the bug is fairly small, so marking as ExternalDependency.
,
Oct 9
,
Nov 26
kbr@: any tips on how to make this and other this kind of bugs closeable?
,
Nov 26
I'd say we can close it once the driver has been released and we can verify the fix with the WebGL test.
,
Nov 26
Kimmo: currently our Linux NVIDIA fleet is running the 384.90 driver: https://cs.chromium.org/chromium/src/testing/buildbot/mixins.pyl?q=mixins.pyl&sq=package:chromium&dr&l=261 If you have a suggested driver we should upgrade them to (could you please verify locally first that the bug is fixed in that version), we can follow the procedures documented here to test that driver and then roll out the upgrade: https://chromium.googlesource.com/chromium/src/+/master/docs/gpu/gpu_testing_bot_details.md#How-to-test-and-deploy-a-driver-update Thanks for your help. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by dglazkov@chromium.org
, Dec 6 2017