http://bugs.winehq.org/show_bug.cgi?id=59380 --- Comment #4 from Henri Verbeet <hverbeet@gmail.com> --- (In reply to Francisco Casas from comment #3)
I am not sure this counts as a vkd3d-shader regression though since I am seeing the same behavior in several older vkd3d versions I tested.
I can only speak for myself, but personally I'm not keeping score like that. In any case, hitting a vkd3d_unreachable() is a problem by definition, and I think that's the minimum we should address for the 1.19 release. Ideally we'd also get this shader to compile correctly, but perhaps that's too ambitious given how close we are to the release. -- 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.