Skip to content

Add diagnostics, derivative uniformity problems trigger diagnostics #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 11 commits into from

Conversation

dneto0
Copy link
Owner

@dneto0 dneto0 commented Dec 13, 2022

Diagnostics may be "filtered" both locally and globally. A filter can drop a matching diagnostic, or change its severity level.

Fixes: gpuweb#3554

@dneto0 dneto0 force-pushed the issue-3554-diag branch 3 times, most recently from a883fae to 3bd8914 Compare December 14, 2022 21:32
dneto0 added 11 commits January 3, 2023 15:42
Diagnostics may be "filtered" both globally and over a range of source
text.
A filter can drop a matching diagnostic, or change its severity level.

Future versions of WGSL can drop a rule too.

Created "diagnostic rule name" token class
- They are spelled like identifier-like things but are not explicitly
  enumerated in the spec.

Fixes: gpuweb#3554
Move definition of triggering location.

Say that error maps to shader-creation and pipeline-creation errors.

Add TODO's related to gpuweb#3682
- Detectable errors will generate diagnostics.

- Most diagnostics are not filterable. They can only be so
  if triggered by one of a few enumerated filterable triggering rules.

- Fix the description of where diagnostics go if processing during
  shader-creaiton or pipeline-creation.
Remove the case where the diagnostic filter applies
to the *arguments* of the targeted call site.
This is under dispute.
See gpuweb#3689
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant