-
Notifications
You must be signed in to change notification settings - Fork 552
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
Fix non-strict HIP device lib order #2217
base: main
Are you sure you want to change the base?
Conversation
could you please add a test for this ? thanks |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2217 +/- ##
==========================================
+ Coverage 30.91% 40.82% +9.91%
==========================================
Files 53 55 +2
Lines 20112 20675 +563
Branches 9755 9801 +46
==========================================
+ Hits 6217 8440 +2223
- Misses 7922 8100 +178
+ Partials 5973 4135 -1838 ☔ View full report in Codecov by Sentry. |
4d87a24
to
c3eb3c5
Compare
Im not 100% sure what the best way is to add the tests, considering that fully testing that issue requires deleting and then re-adding a file from the HIP bitcode directory ( |
e0a58c1
to
48d6ed7
Compare
bump |
still need tests, sorry :) |
4bd15cc
to
3d28979
Compare
3d28979
to
b2355f7
Compare
Seems that fuse doesn't work in github actions. I guess the only other approach swapping out calls to |
Hmm, it might be possible to LD_PRELOAD a library which returns random results from readdir... |
In #2045 initial support for HIP was added. While trying it out, I noticed that different runs across different machines did not yield an expected cache hit. After some investigation, it turns out that the list of bitcode device libraries is not sorted after discovering them from the file system, and this resulted in a different order across those machines. I've added a fix that simply sorts those libraries after discovering them, that seems to be similar to how its handled elsewhere.