Skip to content

Commit

Permalink
[0010] Clarify behavior of vk::aliased_pointer
Browse files Browse the repository at this point in the history
Specifically, clarify interaction with default (restrict) BufferPointer.

Fixes microsoft#87.
  • Loading branch information
greg-lunarg committed Sep 8, 2023
1 parent bbc54fe commit a606931
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion proposals/0010-vk-buffer-ref.md
Original file line number Diff line number Diff line change
Expand Up @@ -184,7 +184,7 @@ Applying HLSL semantic annotations to objects of type vk::BufferPointer is disal

By default, buffer pointers are assumed to be restrict pointers as defined by the C99 standard.

An attribute vk::aliased_pointer can be attached to a variable, function parameter or a block member of buffer pointer type. It is assumed that the pointee of an object with this attribute can overlap with the pointee of any other object with this attribute.
An attribute vk::aliased_pointer can be attached to a variable, function parameter or a block member of BufferPointer type. It ie assumed that the pointee of a BufferPointer with this attribute can overlap with the pointee of any other BufferPointer with this attribute. This also means that the pointee of a BufferPointer with this attribute does not overlap with the pointee of a default (restrict) BufferPointer.

### Buffer Pointers and Address Space

Expand Down

0 comments on commit a606931

Please sign in to comment.