Skip to content
Permalink
Browse files

Change log for May 13, 2019 Vulkan 1.1.108 spec update:

  * Update release number to 108.

Internal Issues:

  * Clarify that only external resources can be bound to external memory in
    valid usage statements for flink:vkBindBufferMemory,
    flink:vkBindImageMemory, slink:VkSparseMemoryBind, and
    slink:VkSparseImageMemoryBind (internal issue 1496).
  * Move all `vk.xml`requirements for
    flink:vkGetDeviceGroupSurfacePresentModes2EXT into
    `<<VK_EXT_full_screen_exclusive>>` (internal issue 1622).
  * Add some missing valid usage statements for
    flink:vkCmdEndQueryIndexedEXT (internal issue 1638).
  * Specify rules for defining "`New Flags and Bitmask Types`" in that
    section of the style guide (internal issue 1649).
  * Add a comment to the `vk.xml` extension block for
    `VK_ANDROID_native_buffer` explaining why the extension is tagged
    `"disabled"` (internal issue 1657).
  * Fix typos in the description of slink:VkImageViewCreateInfo (internal
    issue 1661).
  * Modify valid usage statements for slink:VkImageViewCreateInfo to fix the
    description about the restriction for pname:baseArrayLayer and
    pname:layerCount from pname:extent.depth to the depth of mipmap level
    while creating a 2D array image view on a 3D image.
  * Forbid structures that contain opaque types (images or samplers) in the
    SPIR-V <<spirvenv-module-validation, Validation Rules within a Module>>
    section.
  * Minor editorial changes for the `VK_EXT_swapchain_colorspace` extension
    in the description of slink:VkColorSpace KHR and `vk.xml`, including:
  ** Consistently specify which function (OETF or Inverse-EOTF) is being
     defined;
  ** Remove the Display P3 EOTF, since no other EOTFs are defined;
  ** Include luminance range for the HLG OETF;
  ** Remove a duplicated paragraph; and,
  ** Rename ename:VK_COLOR_SPACE_DISPLAY_P3_LINEAR_EXT, leaving the old
     ename:VK_COLOR_SPACE_DCI_P3_LINEAR_EXT token as an alias.

New Extensions:

  * `<<VK_NV_framebuffer_mixed_samples_coverage_reduction_mode>>`
  * `<<VK_KHR_uniform_buffer_standard_layout>>`
  • Loading branch information...
oddhack committed May 13, 2019
1 parent 5abf83f commit 40ba6e9a4468915aa3aef2ccc153d60e7988193f
@@ -8,6 +8,52 @@ public pull requests that have been accepted.

-----------------------------------------------------

Change log for May 13, 2019 Vulkan 1.1.108 spec update:

* Update release number to 108.

Internal Issues:

* Clarify that only external resources can be bound to external memory in
valid usage statements for flink:vkBindBufferMemory,
flink:vkBindImageMemory, slink:VkSparseMemoryBind, and
slink:VkSparseImageMemoryBind (internal issue 1496).
* Move all `vk.xml`requirements for
flink:vkGetDeviceGroupSurfacePresentModes2EXT into
`<<VK_EXT_full_screen_exclusive>>` (internal issue 1622).
* Add some missing valid usage statements for
flink:vkCmdEndQueryIndexedEXT (internal issue 1638).
* Specify rules for defining "`New Flags and Bitmask Types`" in that
section of the style guide (internal issue 1649).
* Add a comment to the `vk.xml` extension block for
`VK_ANDROID_native_buffer` explaining why the extension is tagged
`"disabled"` (internal issue 1657).
* Fix typos in the description of slink:VkImageViewCreateInfo (internal
issue 1661).
* Modify valid usage statements for slink:VkImageViewCreateInfo to fix the
description about the restriction for pname:baseArrayLayer and
pname:layerCount from pname:extent.depth to the depth of mipmap level
while creating a 2D array image view on a 3D image.
* Forbid structures that contain opaque types (images or samplers) in the
SPIR-V <<spirvenv-module-validation, Validation Rules within a Module>>
section.
* Minor editorial changes for the `VK_EXT_swapchain_colorspace` extension
in the description of slink:VkColorSpace KHR and `vk.xml`, including:
** Consistently specify which function (OETF or Inverse-EOTF) is being
defined;
** Remove the Display P3 EOTF, since no other EOTFs are defined;
** Include luminance range for the HLG OETF;
** Remove a duplicated paragraph; and,
** Rename ename:VK_COLOR_SPACE_DISPLAY_P3_LINEAR_EXT, leaving the old
ename:VK_COLOR_SPACE_DCI_P3_LINEAR_EXT token as an alias.

New Extensions:

* `<<VK_NV_framebuffer_mixed_samples_coverage_reduction_mode>>`
* `<<VK_KHR_uniform_buffer_standard_layout>>`

-----------------------------------------------------

Change log for April 16, 2019 Vulkan 1.1.107 spec update:

* Update release number to 107.
@@ -70,7 +70,7 @@ allspecs: html pdf styleguide registry
allman: manhtmlpages

allchecks:
$(PYTHON) $(SCRIPTS)/check_spec_links.py -Werror
$(PYTHON) $(SCRIPTS)/check_spec_links.py -Werror --ignore_count 0 -Wno_refpage_missing_desc -Wno_refpage_xrefs -Wno_refpage_name -Wno_refpage_unknown_attrib

# Note that the := assignments below are immediate, not deferred, and
# are therefore order-dependent in the Makefile
@@ -121,7 +121,7 @@ VERBOSE =
# ADOCOPTS options for asciidoc->HTML5 output

NOTEOPTS = -a editing-notes -a implementation-guide
PATCHVERSION = 107
PATCHVERSION = 108
ifneq (,$(findstring VK_VERSION_1_1,$(VERSIONS)))
SPECREVISION = 1.1.$(PATCHVERSION)
else
@@ -1,7 +1,7 @@
include::meta/VK_EXT_swapchain_colorspace.txt[]

*Last Modified Date*::
2017-03-15
2019-04-26
*IP Status*::
No known IP claims.
*Contributors*::
@@ -73,3 +73,8 @@ described by separate extension.

* Revision 3, 2017-06-23 (Courtney Goeltzenleuchter)
- Add extended sRGB non-linear enum.

* Revision 4, 2019-04-26 (Graeme Leese)
- Clarify colorspace transfer function usage.
- Refer to normative definitions in the Data Format Specification.
- Clarify DCI-P3 and Display P3 usage.
@@ -0,0 +1,45 @@
// Copyright (c) 2017-2019 Khronos Group. This work is licensed under a
// Creative Commons Attribution 4.0 International License; see
// http://creativecommons.org/licenses/by/4.0/

include::meta/VK_KHR_uniform_buffer_standard_layout.txt[]

*Last Modified Date*::
2019-01-25
*Contributors*::
- Graeme Leese, Broadcom
- Jeff Bolz, NVIDIA
- Tobias Hector, AMD
- Jason Ekstrand, Intel
- Neil Henning, AMD


=== Short Description

Enables tighter array and struct packing to be used with uniform buffers.

=== Description

This extension modifies the alignment rules for uniform buffers, allowing
for tighter packing of arrays and structures.
This allows, for example, the std430 layout, as defined in
https://www.khronos.org/registry/OpenGL/specs/gl/GLSLangSpec.4.60.pdf[GLSL]
to be supported in uniform buffers.

=== New Enum Constants

* Extending elink:VkStructureType:
** ename:VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_UNIFORM_BUFFER_STANDARD_LAYOUT_FEATURES_KHR

=== New Structures

* slink:VkPhysicalDeviceUniformBufferStandardLayoutFeaturesKHR

=== Issues

None.

=== Version History

* Revision 1, 2019-01-25 (Graeme Leese)
- Initial draft
@@ -0,0 +1,73 @@
include::meta/VK_NV_coverage_reduction_mode.txt[]

*Last Modified Date*::
2019-01-29
*Contributors*::
- Kedarnath Thangudu, NVIDIA
- Jeff Bolz, NVIDIA

When using a framebuffer with mixed samples, a per-fragment coverage
reduction operation is performed which generates a color sample mask from
the coverage mask.
This extension defines the following modes to control how this reduction is
performed.

* Merge: When there are more raster samples than color samples, there is
an implementation dependent association of each raster sample to a color
sample.
In the merge mode, the reduced color sample mask is computed such that
the bit for each color sample is 1 if any of the associated bits in the
fragment’s coverage is on, and 0 otherwise.
This is the default mode.

* Truncate: When there are more raster samples (N) than color samples(M),
there is one to one association of the first M raster samples to the M
color samples and the coverage bits for the other raster samples are
ignored.

When the number of raster samples is equal to the color samples, there is a
one to one mapping between them in either of the above modes.

The new command
flink:vkGetPhysicalDeviceSupportedFramebufferMixedSamplesCombinationsNV can
be used to query the various raster, color, depth/stencil sample count and
reduction mode combinations that are supported by the implementation.
This extension would allow an implementation to support the behavior of both
`VK_NV_framebuffer_mixed_samples` and `VK_AMD_mixed_attachment_samples`
extensions simultaneously.


=== New Object Types

None.

=== New Enum Constants

* Extending elink:VkStructureType
** ename:VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_COVERAGE_REDUCTION_MODE_FEATURES_NV
** ename:VK_STRUCTURE_TYPE_PIPELINE_COVERAGE_REDUCTION_STATE_CREATE_INFO_NV
** ename:VK_STRUCTURE_TYPE_FRAMEBUFFER_MIXED_SAMPLES_COMBINATION_NV

=== New Enums

* elink:VkCoverageReductionModeNV
* tlink:VkPipelineCoverageReductionStateCreateFlagsNV

=== New Structures

* slink:VkPhysicalDeviceCoverageReductionModeFeaturesNV
* slink:VkPipelineCoverageReductionStateCreateInfoNV
* slink:VkFramebufferMixedSamplesCombinationNV

=== New Functions

* flink:vkGetPhysicalDeviceSupportedFramebufferMixedSamplesCombinationsNV

=== Issues

None.

=== Version History

* Revision 1, 2019-01-29 (Kedarnath Thangudu)
- Internal revisions
@@ -615,6 +615,7 @@ endif::VK_KHR_shader_float16_int8+!VK_KHR_16bit_storage[]
** Objects of types code:OpTypeImage, code:OpTypeSampler,
code:OpTypeSampledImage, and arrays of these types must: not be stored
to or modified.
* Structure types must: not contain opaque types.
* Decorations
** Any code:BuiltIn decoration not listed in
<<interfaces-builtin-variables>> must: not be used.

0 comments on commit 40ba6e9

Please sign in to comment.
You can’t perform that action at this time.