Revert "Revert frozen RuntimeType objects and write barriers for frozen objects" #76649
Conversation
ghost
added
the
area-CodeGen-coreclr
|
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue DetailsThis PR reverts #76235 with a few manual modifications:
The main issue why the initial PRs (#75573 and #76135) were reverted has just been resolved via #76251 tldr:
|
|
/azp run runtime-coreclr outerloop, runtime-coreclr gcstress0x3-gcstress0xc |
|
Azure Pipelines successfully started running 2 pipeline(s). |
EgorBo
force-pushed
the
foh-frozen-types-2
branch
from
e64a5d5 to
ecc25ea
Compare
Co-authored-by: Jan Kotas <[email protected]>
Co-authored-by: Jan Kotas <[email protected]>
Co-authored-by: Jan Kotas <[email protected]>
Co-authored-by: Jan Kotas <[email protected]>
jkotas
left a comment
jkotas
left a comment
There was a problem hiding this comment.
(I have not reviewed the superpmi files.)
Co-authored-by: Jan Kotas <[email protected]>
|
SPMI failures are expected (jit-ee guid change) |
ghost
locked as resolved and limited conversation to collaborators
3 participants
This PR reverts #76235 with a few manual modifications:
gen.batis invoked (ThunkInput.txt)The rest of the changes are automatically reverted.
The main issue why the initial PRs (#75573 and #76135) were reverted has just been resolved via #76251
tldr:
GC could collect some associated (with frozen objects) objects as unreachable, e.g. it could collect a SyncBlock, WeakReferences and Dependent handles associated with frozen objects which could (e.g. for a short period of time) be indeed unreachable but return back to life after.
Unblocks #76112