Reenable more_tailcalls under GCStress#106287
Merged
jakobbotsch merged 1 commit intodotnet:mainfrom Aug 14, 2024
Merged
Conversation
Member
Author
|
/azp run runtime-coreclr gcstress0x3-gcstress0xc |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Member
Author
|
cc @dotnet/jit-contrib. Looks like this test is passing under GC stress now -- perhaps, as @SingleAccretion suggested, the original issue was around the placement of the bulk write barrier. If so that was likely fixed by #103301. |
Member
|
@AndyAyersMS, please review this PR before RC1 snap, 8/14. |
AndyAyersMS
approved these changes
Aug 13, 2024
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fix #99410