[Piglit] glsl_parser_test: Changes to config section

Brian Paul brianp at vmware.com
Thu Jan 27 11:15:46 PST 2011


On 01/27/2011 10:53 AM, Chad Versace wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> If you write glsl parser tests that explicitly rely on extensions, take
> notice. I have made two changes to the config section of glsl parser test.
>
> 1. Option 'extension' has been renamed to 'require_extensions'. All
> existing tests have been modified to reflect this change.
>
> 2. A new option has been introduced: override_extensions. This option is
> useful for testing extensions that have been implemented in the
> compiler, but are not yet enabled in the driver.
>
> To manually enable an extension, prefix it with '+'. For example:
> - ------------------
> // [config]
> // expect_result: pass
> // glsl_version: 1.30
> // require_extensions: GL_AMD_conservative_depth
> // override_extensions: +GL_AMD_conservative_depth
> // [end config]
>
> #version 130
> #extension GL_AMD_conservative_depth: require
>
> layout (depth_any) out float gl_FragDepth;
>
> float f() {
>      return 0.0;
> }
> - ------------------
>
> Option 'override_extensions' is also capable of manually disabling
> extensions, by prefixing the extension name with '-'.

This is assuming that's Mesa's being tested (with 
MESA_EXTENSION_OVERRIDE), right?

If the driver isn't Mesa-based, will the test just be skipped entirely?

-Brian


More information about the Piglit mailing list