Prefer KHR entrypoints instead of EXT for robustness tests
authorTapani Pälli <tapani.palli@intel.com>
Thu, 5 Apr 2018 05:13:46 +0000 (08:13 +0300)
committerAlexander Galazin <Alexander.Galazin@arm.com>
Wed, 11 Apr 2018 15:49:05 +0000 (11:49 -0400)
commitc693c85a5f9983caab94c3973e6dc0efaae57b0c
treeaa4cbe28138d23dd792037773cf8fae41a06ff34
parentda6c0bebacd21c429aaa0721ee58ff4e230e6f35
Prefer KHR entrypoints instead of EXT for robustness tests

When resolving function entrypoints, framework resolves EXT
entrypoints after KHR to the same pointers. There are drivers that
implement only KHR entrypoints, prefer KHR over EXT so that KHR
entrypoints will be the ones used if both extensions are supported
by the driver.

Components: OpenGL ES
VK-GL-CTS issue: 1107

Affects:
KHR-NoContext.es32.robustness.getnuniform
KHR-NoContext.es32.robustness.readnpixels

Change-Id: Iec5f7cbdd53061e105b3445f7613ee41fccc4553
Signed-off-by: Tapani Pälli <tapani.palli@intel.com>
framework/opengl/wrapper/glwInitExtES.inl
scripts/opengl/src_util.py