Skip to content

Commit

Permalink
Change log for November 4, 2018 Vulkan 1.1.91 spec update:
Browse files Browse the repository at this point in the history
  * Update release number to 91.

Public Issues:

  * Update Ubuntu subsystem build instructions in `BUILD.adoc` (public pull
    request 624).
  * Delete the `VK_KHR_mir_surface` extension from the Specification and
    XML, due to EOL of the only driver known to have supported it, and
    near-EOL of Mir itself (public issue 814).
  * Fix options for some figures that were using old ones (public pull
    request 841).
  * Fix various accidentally repeated words (public pull request 843).
  * Use `time.process_time()`, introduced in Python 3.3, in the scripts
    instead of `time.clock()`, which will be removed in Python 3.8 (public
    pull request 844).

Internal Issues:

  * Update valid usage statements for
    `VK_ANDROID_external_memory_android_hardware_buffer` in
    slink:VkMemoryAllocateInfo,
    slink:VkImportAndroidHardwareBufferInfoANDROID, and
    flink:vkGetAndroidHardwareBufferPropertiesANDROID to actually be
    verifiable (internal issue 1419).
  * Update valid usage statements for
    `VK_ANDROID_external_memory_android_hardware_buffer` in
    slink:VkMemoryAllocateInfo, slink:VkImageCreateInfo, and
    slink:VkImageViewCreateInfo to move valid usage statements in
    doubly-nested bullet points up one level, accomodating limitations of
    the valid usage extraction script that creates `validusage.json`
    (internal issue 1434).
  * Fix typo etext:VK_ACCESS_SHADING_RATE_IMAGE_BIT_NV to the correct
    ename:VK_ACCESS_SHADING_RATE_IMAGE_READ_BIT_NV.
  * Add missing etext:VK_STRUCTURE_TYPE_* tokens to appendices for
    extensions missing them.

New Extensions:

  * `VK_AMD_memory_overallocation_behavior`
  * `VK_NV_ray_tracing`, replacing `VK_NVX_raytracing`
  • Loading branch information
oddhack committed Nov 4, 2018
1 parent 5ec1957 commit e24e42d
Show file tree
Hide file tree
Showing 47 changed files with 2,834 additions and 1,914 deletions.
20 changes: 10 additions & 10 deletions .gitlab/issue_templates/Release checklist.md
Expand Up @@ -16,8 +16,6 @@ will not require Promoter ratification._
_Requirements may be waived by vote of the working group, provided
that a 2/3 majority of non-abstaining vote are in favor._

# Release checklist for _VK_KHR_extension_name_here_

## Preconditions for Call for Votes (CfV)

_A formal CfV is issued following agreement at a Tuesday meeting that a
Expand All @@ -30,7 +28,7 @@ the extension in question_

- [ ] VAP consulted to the extent the WG considers appropriate
- [ ] CTS tests approved with three passing implementations
- [ ] Vulkan specification merged and stable in devel
- [ ] Vulkan API specification merged and stable in devel
- [ ] SPIR-V specification merged and stable
- [ ] GLSL specification merged and stable

Expand All @@ -42,27 +40,29 @@ the extension in question_
## Preconditions for creating public release issue on GitHub

_Delete any of the following preconditions that are not relevant to
the extension in question_
the extension in question. Enter target dates for software artifacts
where indicated. Note that these are targets and may slip._

- [ ] Vulkan specification ratified by Promoters
- [ ] SPIR-V specification ratified by Promoters
- [ ] GLSL specification ratified by Promoters
- [ ] GLSLang implementation approved to merge
- [ ] GLSLang implementation release schedule agreed: target _target-date_
- [ ] Marketing summary written and approved by Vulkan WG and PR team
- [ ] Validation layer implementation approved to merge
- [ ] Loader support approved to merge (for instance extensions)
- [ ] HLSL mapping defined
- [ ] HLSL mapping supported in GLSLang
- [ ] HLSL mapping supported in DXC
- [ ] CTS tests approved to merge
- [ ] SPIR-V tools implementation approved to merge
- [ ] Loader support approved to merge (for instance extensions)
- [ ] Public release approved by Vulkan WG
- [ ] CTS release schedule agreed: target _target-date_
- [ ] SDK release schedule agreed: target _target-date_
- [ ] SPIR-V tools implementation schedule agreed: target _target-date_
- [ ] Public release schedule agreed: target _target-date_

## Preconditions for closing this issue

- [ ] Public release issue items checked off and issue closed

## Additional (Optional) Items
## Additional (Optional) Items

_These additional items are recommended for creation at some
point during or after the release, but are not required at any point._
Expand Down
23 changes: 15 additions & 8 deletions BUILD.adoc
Expand Up @@ -486,9 +486,9 @@ targets.
Platform-specific toolchain instructions follow:

* Microsoft Windows
** <<depends-ubuntu, Ubuntu / Windows 10>>
** <<depends-ubuntu,Ubuntu / Windows 10>>
** <<depends-mingw,MinGW>> (PDF builds not tested)
** <<depends-cygwin, Cygwin>>
** <<depends-cygwin,Cygwin>>
* <<depends-osx,Mac OS X>>
* <<depends-linux,Linux (Debian, Ubuntu, etc.)>>

Expand All @@ -500,11 +500,11 @@ Most of the dependencies on Linux packages are light enough that it's
possible to build the spec natively in Windows, but it means bypassing the
makefile and calling functions directly.
Considering how easy it is to get an Unix subsystem or VM on Windows, this
is not recommended and it is unlikely a direct path will become supported in
the future.
is not recommended.
It is unlikely a direct path will become supported in the future.

There are three supported options for Windows users: Ubuntu / Windows 10,
MinGW, or Cygwin.
Three options for Windows users are described below: Ubuntu / Windows 10
(best, as long as you're running Windows 10), MinGW, and Cygwin.


[[depends-ubuntu]]
Expand Down Expand Up @@ -666,6 +666,13 @@ sudo apt install build-essential python3 git cmake bison flex \
libpango1.0-dev fonts-lyx ghostscript
----

[NOTE]
.Note
====
On Ubuntu versions prior to 18.04 LTS, you will probably need to use the
`ttf-lyx` package instead of `fonts-lyx`.

This comment has been minimized.

Copy link
@krOoze

krOoze Nov 4, 2018

Contributor

Based on Launchpad it seems to be in repo even for Trusty (14.04.5)...

This comment has been minimized.

Copy link
@oddhack

oddhack Nov 5, 2018

Author Contributor

I had an old WSL Ubuntu 14.04 install running and had trouble with that, but it is a NOTE in any event.

====

These instructions are for the Ubuntu installation and are generally
applicable to native Linux environments that use Debian packages, although
the exact list of packages to install may differ.
Expand All @@ -687,7 +694,7 @@ Once the Ruby environment is set up, install the required
[[depends-osx]]
=== Mac OS X

Mac OS X should work in the same way as for ubuntu by using the Homebrew
Mac OS X should work in the same way as for Ubuntu by using the Homebrew
package manager, with the exception that you can simply install the ruby
package via `brew` rather than using a ruby-specific version manager.

Expand Down Expand Up @@ -979,7 +986,7 @@ correctly on future launches.
[[history]]
== Revision History

* 2018-10-25 - Update Troubleshooting, and Windows and Linux build. Plus
* 2018-10-25 - Update Troubleshooting, and Windows and Linux build. Plus
random editing.
* 2018-03-13 - Rename to BUILD.adoc and update for new directory
structure.
Expand Down
2 changes: 1 addition & 1 deletion Makefile
Expand Up @@ -112,7 +112,7 @@ VERBOSE =
# EXTRAATTRIBS sets additional attributes, if passed to make
# ADOCOPTS options for asciidoc->HTML5 output
NOTEOPTS = -a editing-notes -a implementation-guide
PATCHVERSION = 90
PATCHVERSION = 91
ifneq (,$(findstring VK_VERSION_1_1,$(VERSIONS)))
SPECREVISION = 1.1.$(PATCHVERSION)
else
Expand Down
47 changes: 47 additions & 0 deletions appendices/VK_AMD_memory_overallocation_behavior.txt
@@ -0,0 +1,47 @@
include::meta/VK_AMD_memory_overallocation_behavior.txt[]

*Last Modified Date*::
2018-09-19
*IP Status*::
No known IP claims.
*Contributors*::
- Martin Dinkov, AMD
- Matthaeus Chajdas, AMD
- Daniel Rakos, AMD
- Jon Campbell, AMD

This extension allows controlling whether explicit overallocation beyond the
device memory heap sizes (reported by
slink:VkPhysicalDeviceMemoryProperties) is allowed or not.
Overallocation may lead to performance loss and is not supported for all
platforms.

=== New Object Types

None.

=== New Enum Constants

* Extending ename:VkStructureType:
** ename:VK_STRUCTURE_TYPE_DEVICE_MEMORY_OVERALLOCATION_CREATE_INFO_AMD

=== New Enums

* elink:VkMemoryOverallocationBehaviorAMD

=== New Structures

* slink:VkDeviceMemoryOverallocationCreateInfoAMD

=== New Functions

None.

=== Examples

None.

=== Version History

* Revision 1, 2018-09-19 (Martin Dinkov)
- Initial draft.
4 changes: 4 additions & 0 deletions appendices/VK_EXT_conditional_rendering.txt
Expand Up @@ -25,6 +25,10 @@ None.

=== New Enum Constants

* Extending elink:VkStructureType:
** ename:VK_STRUCTURE_TYPE_COMMAND_BUFFER_INHERITANCE_CONDITIONAL_RENDERING_INFO_EXT
** ename:VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_CONDITIONAL_RENDERING_FEATURES_EXT
** ename:VK_STRUCTURE_TYPE_CONDITIONAL_RENDERING_BEGIN_INFO_EXT
* Extending elink:VkAccessFlagBits:
** ename:VK_ACCESS_CONDITIONAL_RENDERING_READ_BIT_EXT
* Extending elink:VkBufferUsageFlagBits:
Expand Down
1 change: 1 addition & 0 deletions appendices/VK_EXT_vertex_attribute_divisor.txt
Expand Up @@ -22,6 +22,7 @@ Extending elink:VkStructureType:

** ename:VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_VERTEX_ATTRIBUTE_DIVISOR_PROPERTIES_EXT
** ename:VK_STRUCTURE_TYPE_PIPELINE_VERTEX_INPUT_DIVISOR_STATE_CREATE_INFO_EXT
** ename:VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_VERTEX_ATTRIBUTE_DIVISOR_FEATURES_EXT

=== New Enums

Expand Down
1 change: 1 addition & 0 deletions appendices/VK_KHR_device_group_creation.txt
Expand Up @@ -27,6 +27,7 @@ None.

* Extending elink:VkStructureType:
** ename:VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_GROUP_PROPERTIES_KHR
** ename:VK_STRUCTURE_TYPE_DEVICE_GROUP_DEVICE_CREATE_INFO_KHR
* Extending elink:VkMemoryHeapFlagBits
** ename:VK_MEMORY_HEAP_MULTI_INSTANCE_BIT_KHR

Expand Down
79 changes: 0 additions & 79 deletions appendices/VK_KHR_mir_surface.txt

This file was deleted.

0 comments on commit e24e42d

Please sign in to comment.