Skip to content

Commit

Permalink
Make headings more consistent, add binding section refs
Browse files Browse the repository at this point in the history
  • Loading branch information
pow2clk committed Nov 2, 2024
1 parent 706242f commit d5604d8
Showing 1 changed file with 5 additions and 9 deletions.
14 changes: 5 additions & 9 deletions specs/language/resources.tex
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
These take the form of Typed Buffers, Raw Buffers, Textures, and Samplers.
Buffer and Texture types can be read-only or writable.

\Sec{Typed Buffers}{Resources.tybuf}
\Sec{Typed Buffers}{Resources.tybufs}

The typed buffer class template represents a one-dimensional resource containing an array of a single given type.
Its contents are indexed by typed access to each element
Expand All @@ -23,8 +23,6 @@
Typed buffers perform format conversions on load such that the underlying data
gets converted to the destination type.

\Sec{Typed Buffers}{Resources.tybufs}

\begin{HLSL}
template <typename T = float4>
class Buffer {
Expand Down Expand Up @@ -71,7 +69,7 @@
\end{HLSL}

When defined at global scope, typed buffers are bound to externally-defined backing stores
using the explicit binding location if provided or the implicit binding if not.
using the explicit binding location if provided or the implicit binding if not (\ref{Resources.binding}).

When defined at local scope, typed buffers represent local references
that can be associated with global buffers when assigned,
Expand Down Expand Up @@ -128,7 +126,7 @@
Partial writes aren't allowed.
Assignment to individual vector elements will result in an error.

\Sec{Raw Buffer Types}{Resources.rawbufs}
\Sec{Raw Buffers}{Resources.rawbufs}

Raw buffers are one-dimensional resources of arbitrary memory layout.
They are either ByteAddressBuffers or StructuredBuffers.
Expand Down Expand Up @@ -250,7 +248,7 @@
\end{HLSL}

When defined at global scope, ByteAccessBuffers are bound to externally-defined backing stores
using the explicit binding location if provided or the implicit binding if not.
using the explicit binding location if provided or the implicit binding if not (\ref{Resources.binding}).

When defined at local scope, ByteAccessBuffers represent local references
that can be associated with global ByteAccessBuffers when assigned,
Expand Down Expand Up @@ -458,8 +456,6 @@
Structured buffers can be defined with scalar, vector, matrix, or user-defined
struct elements.

\Sec{Structured Buffers}{Resources.stbufs}

Structured buffers can be read-only, writable, appendable, or consumable.
Writable buffers can have their elements assigned in arbitrary locations.
Append structured buffers can only have elements added to the end.
Expand Down Expand Up @@ -542,7 +538,7 @@
\end{HLSL}

When defined at global scope, structured buffers are bound to externally-defined backing stores
using the explicit binding location if provided or the implicit binding if not.
using the explicit binding location if provided or the implicit binding if not (\ref{Resources.binding}).

When defined at local scope, structured buffers represent local references
that can be associated with global buffers when assigned,
Expand Down

0 comments on commit d5604d8

Please sign in to comment.