-
Notifications
You must be signed in to change notification settings - Fork 241
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
[HOTFIX][SWDEV-326460] check MIOPEN_DEBUG_CONVOLUTION_DETERMINISTIC in IsApplicable() #1451
Conversation
blocked by #1452, CI will not pass Update: fixed |
This comment was marked as off-topic.
This comment was marked as off-topic.
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.
LGTM, waiting for CI.
@carlushuang I am Ok with this PR, but can you please comment out was is wrong with #1377?
We can, and the library will use the default tuning config instead. The cost is a warning message. |
@JehandadKhan @asroy @zjing14 @atamazov last call for reviewers :) Plan to merge and cherry pick later today 03/08. |
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 OK with this provided that all the affected iGemm solvers use floating-point addition in order to compute sums of values calculated by different work-items.
I highly recommend renaming this PR in order to include "(SWDEV-316705)" into commit name. |
…n IsApplicable() (#1451) * check MIOPEN_DEBUG_CONVOLUTION_DETERMINISTIC in IsApplicable() Co-authored-by: Jun Liu <[email protected]>
This is an hot fix for SWDEV-316705
Due to our current design, if a solver has multiple configs, and some of the config support deterministic(e.g. non-deterministic), some are not, we can not disable a single config in
IsValid()
function. But We need disable it inIsApplicable()
, which means will disable this solver entirely ifMIOPEN_DEBUG_CONVOLUTION_DETERMINISTIC
env var is set.This may have a performance impact, but since currently this env var is for test purpose (in this case performance impact is OK per our customer), so this approach is simple and fine.
If in future has performance requirement under
MIOPEN_DEBUG_CONVOLUTION_DETERMINISTIC
, need to seek for other approach and implementation.