Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
StableHLO Testdata Refresh
Note: Careful attempting to review.. this is all generated by a JAX script to dump their parameterized JAX primitive tests to StableHLO test cases, so the majority of this PR isn't interesting. I'll highlight some interesting bits below. The testgen script will remain an internal tool until it's cleaned up / validated a bit then we can upload it to build_tools.
I noticed that we didn't have any CHLO tests to capture precision changes as we go about making CHLO decompositions more precise.
High level overview
Better names
Better is relative.. but these names are now shorter and more readable, and shouldn't break any users with "max file length too long" anymore.
CustomCalls more closely model Check dialect ops
Pretty much all the same, just no longer do the custom_call's return anything. This will allow us to write a trivial pass to convert to/from check ops, by more closely modeling check ops.
New CHLO tests
Now we have tests that leverage CHLO decompositions and compare them to reference semantics from JAX/XLA.
New bugs discovered ( 😄 )
Filtering a few sort-related bugs on #2440. Note: All disabled tests contain
RUN-DISABLED(reason)
Accuracy filters
Future work
OSS the test generation script
Hopefully can get to this later in the week. Just need to figure out how to go about testing it. At a minimum I'll put it in an gist that may go stale at any time.
Make accuracy constraints tighter
We don't have many accuracy guarantees today, and some of these have fairly loose tolerances. Would be good to make this more strict over time.