aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKarl Schultz <karl@lunarg.com>2016-04-07 10:52:43 -0600
committerKarl Schultz <karl@lunarg.com>2016-04-07 10:52:43 -0600
commit338aa55610c3cf6df2210c19c461638a81d54c85 (patch)
treee22659bc8ad2dc9a97d3e80d992bd7a3b64b6491
parentf2c4f23432f913c332be793dc776a1810ed688b7 (diff)
downloadusermoji-338aa55610c3cf6df2210c19c461638a81d54c85.tar.xz
layers: INVALID_ATTACH_COUNT -> INVALID_ATTACHMENT_COUNT
Fix error reported by vkvalidatelayerdoc test. Change-Id: I7e1bb4e5cb8c113202d479ef95cc0d37334040b1
-rw-r--r--layers/vk_validation_layer_details.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/layers/vk_validation_layer_details.md b/layers/vk_validation_layer_details.md
index 19623e5e..e775fe44 100644
--- a/layers/vk_validation_layer_details.md
+++ b/layers/vk_validation_layer_details.md
@@ -326,7 +326,7 @@ For the second category of errors, VK_LAYER_LUNARG_device_limits stores its own
| Valid instance | If an invalid instance is used, this error will be flagged | INVALID_INSTANCE | vkEnumeratePhysicalDevices | NA | VK_LAYER_LUNARG_object_tracker should also catch this so if we made sure VK_LAYER_LUNARG_object_tracker was always on top, we could avoid this check |
| Valid physical device | Enum used for informational messages | INVALID_PHYSICAL_DEVICE | vkEnumeratePhysicalDevices | NA | VK_LAYER_LUNARG_object_tracker should also catch this so if we made sure VK_LAYER_LUNARG_object_tracker was always on top, we could avoid this check |
| Valid inherited query | If an invalid inherited query is used, this error will be flagged | INVALID_INHERITED_QUERY | vkBeginCommandBuffer | NA | None |
-| Valid attachment count | If the number of attachments exceeds the device max, this error will be flagged | INVALID_ATTACH_COUNT | vkCreateRenderPass | NA | None |
+| Valid attachment count | If the number of attachments exceeds the device max, this error will be flagged | INVALID_ATTACHMENT_COUNT | vkCreateRenderPass | NA | None |
| Querying array counts | For API calls where an array count should be queried with an initial call and a NULL array pointer, verify that such a call was made before making a call with non-null array pointer. | MUST_QUERY_COUNT | vkEnumeratePhysicalDevices vkGetPhysicalDeviceQueueFamilyProperties | NA | Create focused test |
| Array count value | For API calls where an array of details is queried, verify that the size of the requested array matches the size of the array supported by the device. | COUNT_MISMATCH | vkEnumeratePhysicalDevices vkGetPhysicalDeviceQueueFamilyProperties | NA | Create focused test |
| Queue Creation | When creating/requesting queues, make sure that QueueFamilyPropertiesIndex and index/count within that queue family are valid. | INVALID_QUEUE_CREATE_REQUEST | vkGetDeviceQueue vkCreateDevice | NA | Create focused test |