forked from jax-ml/jax
-
Notifications
You must be signed in to change notification settings - Fork 10
Bundle specific and generic arch build targets together. #780
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
Open
tsrw2048
wants to merge
1
commit into
rocm-jaxlib-v0.10.0
Choose a base branch
from
bundle-specific-arch
base: rocm-jaxlib-v0.10.0
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure why we need all of these. Doesn't for example gfx9-4-generic cover gfx950 already?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IIUC this most lilkely fix sort kernel issues , with max_k unit tests???
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if the sort kernel issues are there, why do we add generic targets? why don't we keep specific targets until those issues are fixed?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gulsumgudukbay We can drop generic arch build targets if needed. I was under the impression that we wanted to add them in and test with them so we would have a smoother transition to pure generic build targets in the future. As mentioned earlier, the main issue with generic build targets right now is the max_k tests that use the sort kernel.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe it is better to keep specific targets until the issue is fixed. did we have any doc to track theRock issue @magaonka-amd?
if there's a bug we shouldn't use the generic targets. originally I proposed the generic targets to rocm-jax to reduce wheel size. but if they are buggy with TheRock and since this is the downstream repo (changes like these are candidates to upstream) we should be careful (and wait) in what we upstream.
Or if our goal is to test/track if the bug is fixed in downstream CI, we can keep only generic targets. Right now it will bloat the wheel size because we have duplicate targets
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gulsumgudukbay That makes sense. I will leave these as specific targets for now and close the PR then.