Vulkan CTS 1.3.9.2

New Tests:
 * Allow extra invocations in the pipeline stats

Fixes:
 * Reduce the memory footprint in recursiveTraces*
 * Fix a VkSampler use-after-free in the VK_EXT_descriptor_buffer capture/replay tests
 * Fix VkPipelineShaderStageCreateFlags in dgc tests
 * Fix settings dynamic states in shader object binding test
 * Reduce the memory usage of the compute reconvergence tests
 * Add missing image usage bits in host image copy tests
 * Fix wsi maintenance1 release image tests
 * Add missing NonUniform decoration in variable pointers test
 * Add missing buffer usage flag in raw_access_chain tests
 * Fix creating custom device in push descriptor tests
 * Add missing VkCommandBufferInheritanceInfo in dgc tests
 * Optimize out redundant other.sign() calls
 * Fix enabling features in shader_module_identifier tests
 * Fix offsets in pixel sampling edge tests
 * Fix setting dynamic states in shader object pipeline interaction tests
 * Fix enabling features in bind_buffers_2 tests
 * Fix pWaitDstStageMask in wsi maintenance1 tests
 * Fix tests to use custom device interface that they've created.
 * Fix float comparison: ray_tracing_pipeline.callable_shader*
 * Add extra fast-math decoration in OpPhi tests
 * Enable required features in extended_dynamic_state tests
 * Remove invalid maintenance3 tests with variable descriptor count
 * Fix basic_draw tests with maintenance7 but not nested support
 * Fix pipeline barriers in nested_command_buffers tests
 * Fix deSign's NaN check

Improvements:
 * Update waiver for new Mali-Gx25 devices
 * Fix deDynamicLibrary_open
 * Add watchdog touch to protected mem stacksize tests
Add extra fast-math decoration in OpPhi tests

In the code
    %comp               = OpFOrdGreaterThan %type_bool %arg1 %arg2
the test was applying the correct fast-math decorations to %comp but not
to %arg1 or %arg2. This meant that the compiler was still able to infer
that the inputs to the comparison could not be certain values and
optimise the results accordingly, causing the test to fail. Add the
decorations to %arg1 and %arg2 as well.

Components: Vulkan
Affects: dEQP-VK.spirv_assembly.instruction.*.float_controls2.*.phi_*

Change-Id: I814f379599be167a32ee081f65b7d824ed5929de
(cherry picked from commit 1e26940a32395ecd12e1927a01a9051f88398538)
1 file changed
tree: 8dc8b579032ed37eda64c470283949f9de33e51a
  1. .github/
  2. android/
  3. data/
  4. doc/
  5. execserver/
  6. executor/
  7. external/
  8. framework/
  9. modules/
  10. scripts/
  11. targets/
  12. .clang-format
  13. .editorconfig
  14. .gitattributes
  15. .gitignore
  16. AndroidGen.bp
  17. AndroidKhronosCTSGen.bp
  18. CMakeLists.txt
  19. CODE_OF_CONDUCT.md
  20. deqp_binary.lds
  21. format_all.sh
  22. LICENSE
  23. METADATA
  24. MODULE_LICENSE_APACHE2
  25. NOTICE
  26. OWNERS
  27. README.md
README.md

VK-GL-CTS README

This repository contains Khronos Conformance Testing Suite called VK-GL-CTS which originated from dEQP (drawElements Quality Program). VK-GL-CTS contains tests for several graphics APIs, including OpenGL, OpenGL ES, EGL, Vulkan, and Vulkan SC.

Documentation

Up-to-date documentation for VK-GL-CTS is available at:

The .qpa logs generated by the conformance tests may contain embedded PNG images of the results. These can be viewed with scripts/qpa_image_viewer.html, by opening the file with a web browser and following its instructions, or using the Cherry tool.

Khronos Vulkan Conformance Tests

This repository includes Khronos Vulkan CTS under external/vulkancts directory. For more information see Vulkan CTS README.

Khronos OpenGL / OpenGL ES Conformance Tests

This repository includes Khronos OpenGL / OpenGL ES CTS under external/openglcts directory. For more information see OpenGL / OpenGL ES CTS README.

Selecting a subset of targets to build by default

When configuring the source code of VK-GL-CTS for running either Vulkan Conformance Tests or OpenGL(ES) Conformance Tests as described above, CMake will generate build files that, by default on desktop platforms, will build every possible project binary. This may be undesirable due the amount of time and disk space needed to perform the build.

One way of selecting only a subset of the targets to be built is using CMake's target selection mechanism. For example, the following command will only build deqp-vk, the main Vulkan Conformance Tests binary:

cmake --build BUILD_DIRECTORY --target deqp-vk

When building only a subset of targets is the preferred default behavior for a given working copy or build directory, there's a second target selection mechanism that can be used to avoid passing the --target option every time: the SELECTED_BUILD_TARGETS CMake option. If set to a non-empty value, only the targets listed in that configuration option, separated by spaces, will be built.

For example, passing -DSELECTED_BUILD_TARGETS="deqp-vk deqp-vksc" when configuring the project will make cmake --build BUILD_DIRECTORY act as if it had been passed --target deqp-vk --target deqp-vksc as additional arguments.

IMPORTANT: Target subset selection may not have been thoroughly tested in all enviroments and situations, and it does not replace the instructions given for the purposes of creating a conformance submission.

ANGLE for Android

ANGLE can be built for Android by following the instructions here.

The resulting ANGLE shared object libraries can be linked against and embedded into dEQP.apk with the --angle-path option. This will cause dEQP.apk to use the ANGLE libraries for OpenGL ES calls, rather than the native drivers.

An ABI must be specified and the directory structure containing the ANGLE shared objects must match it so the build system can find the correct *.so files.

Assuming ANGLE shared objects are generated into ~/chromium/src/out/Release/ and dEQP.apk will be generated with --abis arm64-v8a, issue the following commands:

cd ~/chromium/src/out/Release/
mkdir arm64-v8a && cd arm64-v8a
cp ../lib*_angle.so .

The --angle-path ~/chromium/src/out/Release/ option can then be used to link against and embed the ANGLE shared object files. The full command would be:

python scripts/android/build_apk.py --sdk <path to Android SDK> --ndk <path to Android NDK> --abis arm64-v8a --angle-path ~/chromium/src/out/Release/