Fix wrong image usage flags in api feature info tests
authorSzymon Szczyrbak <szymon.szczyrbak@intel.com>
Mon, 24 Jun 2019 07:21:33 +0000 (09:21 +0200)
committerSlawomir Cygan <slawomir.cygan@intel.com>
Tue, 25 Jun 2019 13:31:47 +0000 (15:31 +0200)
commit0c8c7865ad3695dac93d50eebf0d470c766817a8
treeb8cd12acfce26806bd6e6b097062e0c9255f54d8
parentb1dbc3a460dade3455a85d54aad4358f9d4b5541
Fix wrong image usage flags in api feature info tests

According to spec:
  "If usage includes VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT, usage must
   also contain at least one of VK_IMAGE_USAGE_COLOR_ATTACHMENT_BIT,
   VK_IMAGE_USAGE_DEPTH_STENCIL_ATTACHMENT_BIT, or
   VK_IMAGE_USAGE_INPUT_ATTACHMENT_BIT."

This change adds isValidImageUsageFlagCombination() checks, so invalid
usage flag combinations are not used in test.

VK-GL-CTS Issue: 1850

Components: Vulkan

Affects:
    dEQP-VK.api.info.image_format_properties2.*
    dEQP-VK.api.info.sparse_image_format_properties2.*

Change-Id: Ibc0249686c6ee91ab3758918ab4067694730134c
external/vulkancts/modules/vulkan/api/vktApiFeatureInfo.cpp