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.
Follow up to #7659
Was trying to track down some of these other WriteBarrier assigns in the traces where they didn't need to be there.
The
BufferWriter
.ctor performs a WriteBarrier assign as it doesn't know if its copying the reference to stack or to heap:You might think as its a
ref struct
it can only be stack so doesn't need to use a writebarrrier assign in case of heap; and you'd be right and there is a Jit issue for that: https://github.com/dotnet/coreclr/issues/15755Inlining the .ctor changes the call site from (write barrier behind
BufferWriter'1:.ctor(ref):this
):To the following where there is no WriteBarrier as the Jit can "see" its lifetime is stack only:
/cc @davidfowl @jkotalik