http://bugs.winehq.org/show_bug.cgi?id=59687 Francisco Casas <fcasas@codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fcasas@codeweavers.com --- Comment #4 from Francisco Casas <fcasas@codeweavers.com> --- Hi, thank you for the detailed Bug report, and Zeb for the additional insights. This should be fixed by https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/1997
Corollary question so I don't forget it: should we even be checking CONST at all here? Whether a variable is resolvable to a compile time constant doesn't really depend on whether it's marked const at all.
I think whether it is CONST or not matters, consider the following shader: ``` float4 main() : sv_target { const int b = 4; float arr[b]; return 0; } ``` compilation fails in native if 'const' is removed. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.