mirror of
https://github.com/libsdl-org/SDL.git
synced 2026-08-26 00:21:39 +00:00
Sync SDL3 wiki -> header
[ci skip]
This commit is contained in:
@@ -883,8 +883,8 @@ typedef enum SDL_GPUTextureFormat
|
||||
/**
|
||||
* Specifies how a texture is intended to be used by the client.
|
||||
*
|
||||
* A texture must have at least one usage flag.
|
||||
* Note that combining SAMPLER with STORAGE_READ flags is invalid.
|
||||
* A texture must have at least one usage flag. Note that combining SAMPLER
|
||||
* with STORAGE_READ flags is invalid.
|
||||
*
|
||||
* With regards to compute storage usage, READ | WRITE means that you can have
|
||||
* shader A that only writes into the texture and shader B that only reads
|
||||
@@ -967,9 +967,10 @@ typedef enum SDL_GPUCubeMapFace
|
||||
* Specifies how a buffer is intended to be used by the client.
|
||||
*
|
||||
* A buffer must have at least one usage flag.
|
||||
*
|
||||
* If a buffer has multiple read usages, this may lead to a performance penalty
|
||||
* due to more conservative memory barriers, but it also may not necessarily affect the performance.
|
||||
*
|
||||
* If a buffer has multiple read usages, this may lead to a performance
|
||||
* penalty due to more conservative memory barriers, but it also may not
|
||||
* necessarily affect the performance.
|
||||
*
|
||||
* Unlike textures, READ | WRITE can be used for simultaneous read-write
|
||||
* usage. The same data synchronization concerns as textures apply.
|
||||
|
||||
Reference in New Issue
Block a user