Fix problem with flags fp32 and int8 #27954
Merged
Conversation
This file contains 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
|
Thanks for your contribution! |
MingMingShangTian
pushed a commit
to MingMingShangTian/Paddle
that referenced
this pull request
Oct 15, 2020
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.
PR types
Bug fixes
PR changes
APIs
Describe
This PR fixes problem with different uses of flags
--enable_int8,--enable_fp32and--enable_bf16.Bfloat16 test for image classification models uses the same functions as int8 and quant tests and the default value for
--enable_int8and--enable_fp32is true that is why after adding--enable_bf16there were some conflicts.This PR changes the default value for
enable_int8and--enable_bf16tofalseand adds setting these flags to every test in CMake files.