anv: Stop including POS in FS input limits
authorJason Ekstrand <jason@jlekstrand.net>
Mon, 29 Apr 2019 05:46:10 +0000 (00:46 -0500)
committerJason Ekstrand <jason@jlekstrand.net>
Thu, 2 May 2019 23:56:51 +0000 (18:56 -0500)
It is an input but it comes in as part of the shader payload and doesn't
count towards the limits.

Reviewed-by: Kenneth Graunke <kenneth@whitecape.org>
src/intel/vulkan/anv_device.c

index ef2c9b50193e6434cc9a34035a963ba796c82ca2..507b81e0d3a7163fbf2077a98721d7545c6ade3f 100644 (file)
@@ -1249,7 +1249,7 @@ void anv_GetPhysicalDeviceProperties(
       .maxGeometryOutputComponents              = 128,
       .maxGeometryOutputVertices                = 256,
       .maxGeometryTotalOutputComponents         = 1024,
-      .maxFragmentInputComponents               = 112, /* 128 components - (POS, PSIZ, CLIP_DIST0, CLIP_DIST1) */
+      .maxFragmentInputComponents               = 116, /* 128 components - (PSIZ, CLIP_DIST0, CLIP_DIST1) */
       .maxFragmentOutputAttachments             = 8,
       .maxFragmentDualSrcAttachments            = 1,
       .maxFragmentCombinedOutputResources       = 8,