[AutoScheduler] Fix FLOPS estimation #8695
Merged
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.
The AutoScheduler FLOP estimator now mis-estimates the following case to be 0 FLOPS:
This is because the expression
A[i] > 0
has output dtypeuint
while the input dtypes arefloat32
. In this case the current FLOP estimater ignores the comparison flops. The original concern behinds this logic is to avoid counting index calculation, but we need to make it more general to cover the above case.cc @merrymercy