Stop overriding range_num_stages and range_unroll_factor for CUDA IMA workarounds#2394
Draft
choijon5 wants to merge 1 commit into
Draft
Stop overriding range_num_stages and range_unroll_factor for CUDA IMA workarounds#2394choijon5 wants to merge 1 commit into
choijon5 wants to merge 1 commit into
Conversation
… workarounds stack-info: PR: #2394, branch: choijon5/stack/60
choijon5
force-pushed
the
choijon5/stack/60
branch
from
3424ff6 to
3ba45d9
Compare
meta-cla
Bot
added
the
CLA Signed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Stacked PRs:
With subprocess benchmarking, we no longer need the CUDA IMA workarounds which were made for #755 and #904.
With the workaround removed, CUDA IMA is avoided with subprocess benchmarking, while retaining the same speedup for the JSD kernel as before which needed the workaroud (#733):
