Merge pull request #613 from krOoze/fix_broken_links

Fix broken links
This commit is contained in:
Jon Leech 2017-12-19 01:20:13 -08:00 committed by GitHub
commit f22feb97af
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
7 changed files with 26 additions and 18 deletions

View File

@ -6,7 +6,7 @@ include::meta/VK_AMD_shader_fragment_mask.txt[]
No known IP claims.
*Dependencies*::
- Requires the
https://www.khronos.org/registry/spir-v/extensions/AMD/SPV_AMD_fragment_mask.html[+SPV_AMD_fragment_mask+]
https://www.khronos.org/registry/spir-v/extensions/AMD/SPV_AMD_shader_fragment_mask.html[+SPV_AMD_shader_fragment_mask+]
SPIR-V extension.
*Contributors*::
- Aaron Hagan, AMD
@ -44,8 +44,8 @@ None.
=== New SPIR-V Capabilities
* <<spirvenv-capabilities-table-shaderfragmentmaskamd,
code:ShaderFragmentMaskAMD>>
* <<spirvenv-capabilities-table-fragmentmaskamd,
code:FragmentMaskAMD>>
=== New Structures

View File

@ -114,6 +114,10 @@ ifdef::VK_AMD_texture_gather_bias_lod[]
[[spirvenv-capabilities-table-imagegatherbiaslodamd]]
| code:ImageGatherBiasLodAMD | <<VK_AMD_texture_gather_bias_lod,VK_AMD_texture_gather_bias_lod>>
endif::VK_AMD_texture_gather_bias_lod[]
ifdef::VK_AMD_shader_fragment_mask[]
[[spirvenv-capabilities-table-fragmentmaskamd]]
| code:FragmentMaskAMD | <<VK_AMD_shader_fragment_mask,VK_AMD_shader_fragment_mask>>
endif::VK_AMD_shader_fragment_mask[]
ifdef::VK_NV_sample_mask_override_coverage[]
[[spirvenv-capabilities-table-samplemaskoverridecoverage]]
| code:SampleMaskOverrideCoverageNV | <<VK_NV_sample_mask_override_coverage,VK_NV_sample_mask_override_coverage>>
@ -178,6 +182,11 @@ The application can: pass a SPIR-V module to flink:vkCreateShaderModule that
uses the +SPV_AMD_shader_ballot+ SPIR-V extension.
endif::VK_AMD_shader_ballot[]
ifdef::VK_AMD_shader_fragment_mask[]
The application can: pass a SPIR-V module to flink:vkCreateShaderModule that
uses the +SPV_AMD_shader_fragment_mask+ SPIR-V extension.
endif::VK_AMD_shader_fragment_mask[]
ifdef::VK_AMD_shader_image_load_store_lod[]
The application can: pass a SPIR-V module to flink:vkCreateShaderModule that
uses the +SPV_AMD_shader_image_load_store_lod+ SPIR-V extension.

View File

@ -1604,10 +1604,9 @@ range.
size and alignment in bytes that bounds concurrent access to
<<memory-device-hostaccess, host-mapped device memory>>.
ifdef::VK_EXT_discard_rectangles[]
* [[features-limits-maxDiscardRectangles]] pname:maxDiscardRectangles is
the maximum number of active discard rectangles.
pname:maxDiscardRectangles is a member of the
slink:VkPhysicalDeviceDiscardRectanglePropertiesEXT structure.
* [[features-limits-maxDiscardRectangles]]
slink:VkPhysicalDeviceDiscardRectanglePropertiesEXT::pname:maxDiscardRectangles
is the maximum number of active discard rectangles.
This limit can be queried by setting the pname:pNext pointer from a
slink:VkPhysicalDeviceProperties2KHR object to an instance of
slink:VkPhysicalDeviceDiscardRectanglePropertiesEXT and using
@ -1728,8 +1727,8 @@ include::../api/structs/VkPhysicalDeviceDiscardRectanglePropertiesEXT.txt[]
The members of the sname:VkPhysicalDeviceDiscardRectanglePropertiesEXT
structure describe the following implementation-dependent limits:
* [[features-limits-maxDiscardRectangles]] pname:maxDiscardRectangles is
the maximum number of discard rectangles that can: be specified.
* pname:maxDiscardRectangles is the maximum number of discard rectangles
that can: be specified.
include::../validity/structs/VkPhysicalDeviceDiscardRectanglePropertiesEXT.txt[]

View File

@ -380,7 +380,7 @@ endif::VK_KHR_16bit_storage[]
Composites of these types are also permitted.
If the color attachment has a signed or unsigned normalized fixed-point
format, color values are assumed to be floating-point and are converted to
fixed-point as described in <<fundamentals-fpfixedfpconv>>; If the color
fixed-point as described in <<fundamentals-fpfixedconv>>; If the color
attachment has an integer format, color values are assumed to be integers
and converted to the bit-depth of the target.
Any value that cannot be represented in the attachment's format is

View File

@ -96,7 +96,7 @@ are more efficient than the one specified.
Issues with and bug reports on the Vulkan Specification and the API Registry
can: be filed in the Khronos Vulkan GitHub repository, located at URL
http://github.com/KhronosGroup/Vulkan-Docs
https://github.com/KhronosGroup/Vulkan-Docs
Please tag issues with appropriate labels, such as "`Specification`", "`Ref
Pages`" or "`Registry`", to help us triage and assign them appropriately.
@ -194,7 +194,7 @@ http://dx.doi.org/10.1109/IEEESTD.2008.4610935, August, 2008.
[[data-format]] A. Garrard, _Khronos Data Format Specification, version
1.2_,
https://www.khronos.org/registry/dataformat/specs/1.2/dataformat.1.2.html,
https://www.khronos.org/registry/DataFormat/specs/1.2/dataformat.1.2.html,
September, 2017.
// If the author name is placed on a standalone line, we see the mysterious

View File

@ -549,11 +549,11 @@ elink:VkTessellationDomainOriginKHR enumeration:
include::../api/enums/VkTessellationDomainOriginKHR.txt[]
* ename:VK_TESSELLATION_DOMAIN_ORIGIN_UPPER_LEFT_KHR indicates that the
origin of the domain space is in the upper left corner, flipped
vertically from what is shown in figure <<img-tessellation-topology>>.
origin of the domain space is in the upper left corner, as shown in
figure <<img-tessellation-topology-ul>>.
* ename:VK_TESSELLATION_DOMAIN_ORIGIN_LOWER_LEFT_KHR indicates that the
origin of the domain space is in the lower left corner, as shown in
figure <<img-tessellation-topology>>.
figure <<img-tessellation-topology-ll>>.
This enum affects how the code:VertexOrderCw and code:VertexOrderCcw
tessellation execution modes are interpreted, since the winding is defined

View File

@ -340,8 +340,8 @@ values.
ifdef::VK_KHR_sampler_ycbcr_conversion[]
If <<textures-chroma-reconstruction,Chroma Reconstruction>> is implicit,
<<textures-filtering, Texel Filtering>> instead takes place during chroma
reconstruction, before <<textures-sampler-YCbCr-conversion,sampler
<<textures-texel-filtering, Texel Filtering>> instead takes place during
chroma reconstruction, before <<textures-sampler-YCbCr-conversion,sampler
Y'C~B~C~R~ conversion>> occurs.
endif::VK_KHR_sampler_ycbcr_conversion[]
@ -870,7 +870,7 @@ ename:VK_FORMAT_FEATURE_SAMPLED_IMAGE_YCBCR_CONVERSION_CHROMA_RECONSTRUCTION_EXP
or the sname:VkSamplerYcbcrConversionCreateInfoKHR's
pname:forceExplicitReconstruction is set to ename:VK_TRUE, reconstruction is
performed as an explicit step independent of filtering, described in the
<<textures-explict-reconstruction,Explicit Reconstruction>> section.
<<textures-explicit-reconstruction>> section.
If the format of the image that is to be sampled does not set
ename:VK_FORMAT_FEATURE_SAMPLED_IMAGE_YCBCR_CONVERSION_CHROMA_RECONSTRUCTION_EXPLICIT_BIT_KHR