Allow more complex methods to be compiled under aggressive optimization #7957
Conversation
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
0xdaryl
force-pushed
the
aggressiveopt
branch
from
6601ee6 to
957e091
Compare
A number of applications that care about aggressive throughput performance fail compilations because these compile thresholds are exceeded. While the defaults are still good for most methods, enabling these options in an aggressive compilation mode will allow those methods to succeed more often. Signed-off-by: Daryl Maier <[email protected]>
0xdaryl
force-pushed
the
aggressiveopt
branch
from
957e091 to
0700c95
Compare
|
I think we should try a larger number of apps to make sure they are not adversely affected by this change. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
A number of applications that care about aggressive throughput performance fail compilations because these compile thresholds are exceeded. While the defaults are still good for most methods, enabling these options in an aggressive compilation mode will allow those methods to succeed more often.