Skip to content

Fill out scope explanations and collective operations#2351

Merged
dneto0 merged 2 commits intogpuweb:mainfrom
alan-baker:scope-explanation
Nov 29, 2021
Merged

Fill out scope explanations and collective operations#2351
dneto0 merged 2 commits intogpuweb:mainfrom
alan-baker:scope-explanation

Conversation

@alan-baker
Copy link
Contributor

  • Fix the memory scope for non-private reads and writes missed in Fixes to memory model for barriers and atomics #2297
    • only atomics have device memory scope
  • Define and explain memory and execution scopes
    • add links in atomic and sync built-in function sections
  • Define a quad for the purpose of an implicit execution scope on
    derivatives
  • Remove todos from collective operations
    • fill out barrier, defining control barrier

* Fix the memory scope for non-private reads and writes missed in gpuweb#2297
  * only atomics have device memory scope
* Define and explain memory and execution scopes
  * add links in atomic and sync built-in function sections
* Define a quad for the purpose of an implicit execution scope on
  derivatives
* Remove todos from collective operations
  * fill out barrier, defining control barrier
@alan-baker alan-baker added the wgsl WebGPU Shading Language Issues label Nov 29, 2021
@github-actions
Copy link
Contributor

Previews, as seen when this build job started (07bfa72):
WebGPU | IDL
WGSL
Explainer

Copy link
Contributor

@dneto0 dneto0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking good.
Suggesting some small editorial changes.

wgsl/index.bs Outdated

When an invocation performs a scoped operation, it will affect one or two sets
of invocations.
These sets are the <dfn noexport>memory scope</dfn> and the <dfn
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Editorially I'd make these forward references, and put the defining tags at the sentences on lines 7413.

 The <dfn>memory scope</dfn> of an operation specifies the set of invocations to
  which the operation will be visible....

The "will be visible" is a little bit mysterious. How about:

  The <dfn>memory scope</dfn> of an operation specifies the set of invocations
  whose view of memory will be affected by that operation.

or

  The <dfn>memory scope</dfn> of an operation specifies the set of invocations
  whose interactions with memory will be affected by that operation.

* move definitions to more appropriate locations
* attempt to further clarify memory scope
@github-actions
Copy link
Contributor

Previews, as seen when this build job started (6259fc8):
WebGPU | IDL
WGSL
Explainer

Copy link
Contributor

@dneto0 dneto0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks!

@dneto0 dneto0 merged commit 2d7d03d into gpuweb:main Nov 29, 2021
github-actions bot added a commit that referenced this pull request Nov 29, 2021
SHA: 2d7d03d
Reason: push, by @dneto0

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
github-actions bot added a commit that referenced this pull request Nov 29, 2021
SHA: 2d7d03d
Reason: push, by @dneto0

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
github-actions bot added a commit that referenced this pull request Nov 29, 2021
SHA: 2d7d03d
Reason: push, by @dneto0

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@alan-baker alan-baker deleted the scope-explanation branch November 30, 2021 17:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

wgsl WebGPU Shading Language Issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants