-
Notifications
You must be signed in to change notification settings - Fork 50
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
Use LLVM's byval instead of rewriting kernels. #16
Conversation
Codecov Report
@@ Coverage Diff @@
## master #16 +/- ##
==========================================
- Coverage 68.16% 66.73% -1.44%
==========================================
Files 18 18
Lines 1087 1034 -53
==========================================
- Hits 741 690 -51
+ Misses 346 344 -2
Continue to review full report at Codecov.
|
@jpsamaroo this triggers a bunch of address space-related issues with AMDGPUnative... Are those related to #13? Because the GCN tests in GPUCompiler do pass. |
No those are new https://github.com/llvm/llvm-project/blob/d359f2096850c68b708bc25a7baca4282945949f/llvm/lib/Target/AMDGPU/AMDGPUAliasAnalysis.cpp#L91-L100 By rewriting the kernel we have sofar tricked out the AA for AMDGPU. |
Ah, this only used to fail when testing AMDGPUnative, not during GPUCompiler's GCN tests (maybe codegen tests covering the same functionality should be put here?), and AMD CI is down... |
AMDGPU CI should be back up. The issues with "pointer address space out of range" are due to Julia's optimization pipeline running the verifier at the beginning on debug builds, which #30 should hopefully fix for GCN. |
a634826
to
4f460f8
Compare
Turns out there's a problem with this on Julia 1.4: NVPTX lowers |
No description provided.