compiler/glsl: fix volatile string

The reason the member has a leading underscore is because volatile is a
keyword in C. We don't want to carry that detail into the error-string,
so let's drop the underscore.

Reviewed-by: Matt Turner <mattst88@gmail.com>
Reviewed-by: Ian Romanick <ian.d.romanick@intel.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/9896>
This commit is contained in:
Erik Faye-Lund
2021-03-31 10:09:58 +02:00
committed by Marge Bot
parent 01e012dab8
commit d5e0be9342

View File

@@ -876,7 +876,7 @@ ast_type_qualifier::validate_flags(YYLTYPE *loc,
bad.flags.q.early_fragment_tests ? " early_fragment_tests" : "", bad.flags.q.early_fragment_tests ? " early_fragment_tests" : "",
bad.flags.q.explicit_image_format ? " image_format" : "", bad.flags.q.explicit_image_format ? " image_format" : "",
bad.flags.q.coherent ? " coherent" : "", bad.flags.q.coherent ? " coherent" : "",
bad.flags.q._volatile ? " _volatile" : "", bad.flags.q._volatile ? " volatile" : "",
bad.flags.q.restrict_flag ? " restrict_flag" : "", bad.flags.q.restrict_flag ? " restrict_flag" : "",
bad.flags.q.read_only ? " read_only" : "", bad.flags.q.read_only ? " read_only" : "",
bad.flags.q.write_only ? " write_only" : "", bad.flags.q.write_only ? " write_only" : "",