Add --enable-unsafe-fp-math flag when -O3 and NNPA is used #2963
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
AlexandreEichenberger
approved these changes
Oct 2, 2024
| // Enable aggressive optimization for NNPA with -O3 | ||
| if (OptimizationLevel == OptLevel::O3 && | ||
| getTargetAccel().find("NNPA") != std::string::npos && | ||
| getLLVMOption().find("enable-unsafe-fp-math") == std::string::npos) { |
There was a problem hiding this comment.
I see, the idea is that you just check if that opt is already there. If it's there, either its true and there is no need to add it again, or false and then we don't add it also. Clever.
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.
Since NNPA uses less precise data, it is reasonable to enable aggressive optimization.
Add the flag only for O3, leaving O0 for debugging.