-
Notifications
You must be signed in to change notification settings - Fork 44
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
Track UT gaps for LLVM-path vs SPIRV-path. #223
Comments
UT Status in main branch SPIRV-path============ Overview ============ UT failed cases in llvm-target branch: llvm-path============ Overview (core tests) ============ xfail casestest_core.py::test_atomic_rmw #152 cuda onlytest_core.py::test_globaltimer skipped as FIXME issuetest_core.py::test_scan2d #153 NoteNo more cases passed in spirv-path but failed in llvm-path in language cases. Non-language cases not ported and enabled in llvm-pathNon-language cases ported and PASSED in SPIRV-PATH (issues tracked)operators/test_blocksparse.py::test_softmax[64-1871-False] operators/test_blocksparse.py::test_attention_fwd_bwd[dtype0-16] |
Overall I would say no surprises here. This information was known already, I have opened issues to track the functional problems which are also linked in this work item. |
closing, find specified work item from opening issues, feel free to reopen |
llvm branch have reached the parity with the spirv on the ut pass rate |
Issue Description
Collect the latest UT report for both LLVM-path and SPIRV-path, check the failed cases. High priority for fixing those bugs which failed in LLVM-path while pass in SPIRV-path.
Code Example
System Info
The text was updated successfully, but these errors were encountered: