[ARITH] fix int set analysis on negative scale#9776
Merged
Conversation
MasterJH5574
approved these changes
Dec 20, 2021
MasterJH5574
left a comment
Contributor
There was a problem hiding this comment.
LGTM, and thanks Siyuan for the fix! We seldom encountered the negative-scale cases before, so it's really a nice fix!
junrushao
approved these changes
Dec 20, 2021
Member
|
Thanks for the fix! |
ylc
pushed a commit
to ylc/tvm
that referenced
this pull request
Jan 7, 2022
ylc
pushed a commit
to ylc/tvm
that referenced
this pull request
Jan 13, 2022
qsqqsqqsq-intellif
pushed a commit
to qsqqsqqsq-intellif/tvm
that referenced
this pull request
Apr 29, 2022
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
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.
EstimateRegionLowerBounddid not consider the case that scales are negative.For example, the range
[1 - i, 5 - i), wherei in [0, 4). So the estimated region lower bound should be[-2, 5).By mistake, we analyze it into
[1, 1]previously.cc @junrushao1994 @spectrometerHBH