Update runners & fix JIT tiering hashcode bug #9
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
When using tiered compilation, the method can switch from use of e.g. UnstableHashNonVectorLower and UnstableHashVec256Lower . However, these algorithms produce different results. Therefore, we force compilation of final Jit Tier (Tier 2) by forcing the AggressiveOptimization flag
Sewer56
force-pushed
the
update-runners-fix-hashcode-bug
branch
from
fb9d15b to
63b584b
Compare
Member
Author
|
Also disabled .NET 5 on Ubuntu, no longer supported on runner image due to libssl version. (too new?) |
Sewer56
force-pushed
the
update-runners-fix-hashcode-bug
branch
from
f9c1c03 to
5c84e09
Compare
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.
When using tiered compilation, the method can switch from use of e.g. UnstableHashNonVectorLower and UnstableHashVec256Lower .
However, these algorithms produce different results. Therefore, we force compilation of final Jit Tier (Tier 2) by forcing the AggressiveOptimization flag