On 02/12/2014 12:25 PM, Brian Paul wrote:
> To fix MSVC compile breakage. Evidently, _restrict is an MSVC keyword,
> though the docs only mention __restrict (with two underscores).
Clear violation of the C standard. Strong work. This is almost as bad
as the "near" and "far" rubbish. I'm waitin
To fix MSVC compile breakage. Evidently, _restrict is an MSVC keyword,
though the docs only mention __restrict (with two underscores).
Note: we may want to also rename _volatile to volatile_flag to be
consistent.
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=74900
---
src/glsl/ast.h