Clarify memory locations accessed when writing a vector component #2152
Conversation
Fixes gpuweb#2112 * Write accesses to a vector component may access all memory locations associated with the vector
|
|
||
| #### Component reference from vector reference #### {#component-reference-from-vector-reference} | ||
|
|
||
| A [=write access=] to component of a vector **may** access all of the [=memory |
There was a problem hiding this comment.
I'm not sure this is the ideal spec section to specify this, but it felt better than specifying it in the memory access mode, memory locations or memory layout sections.
There was a problem hiding this comment.
This is as good a place as any, until #2055 lands.
When that lands, its normative spot would be around the statement:
A memory operation accesses exactly the set of [=memory location|locations=]
associated with the particular [=memory view=] used in the operation.
Because the two statements are in conflict, and the exception overrules the general case.
|
|
||
| #### Component reference from vector reference #### {#component-reference-from-vector-reference} | ||
|
|
||
| A [=write access=] to component of a vector **may** access all of the [=memory |
There was a problem hiding this comment.
This is as good a place as any, until #2055 lands.
When that lands, its normative spot would be around the statement:
A memory operation accesses exactly the set of [=memory location|locations=]
associated with the particular [=memory view=] used in the operation.
Because the two statements are in conflict, and the exception overrules the general case.
WGSL meeting minutes 2021-10-05
|
Fixes #2112
associated with the vector