VSadov/Satori
1
0
Fork 0
mirror of https://github.com/VSadov/Satori.git synced 2025-06-09 17:44:48 +09:00
Code Activity

Updated Garbage Collector design document URL

Browse source 
Commit migrated from 3fce00cd4a
This commit is contained in:
Eddie Hedges 2015-05-07 15:51:54 -05:00
parent 3c2a3db2e7
commit 50657d0a49
1 changed files with 1 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

3
docs/coreclr/intro-to-clr.md
View file

@ -88,8 +88,7 @@ At any time some other thread of execution might perform an allocation that requ
What this means is that the CLR needs to track _all_ references to the GC heap _almost_ all the time. Since GC references may reside in machine registers, in local variables, statics, or other fields, there is quite a bit to track. The most problematic of these locations are machine registers and local variables because they are so intimately related to the actual execution of user code. Effectively, what this means is that the _machine code_ that manipulates GC references has another requirement: it must track all the GC references that it uses. This implies some extra work for the compiler to emit the instructions to track the references.
TODO: Update GC BOTR link
To learn more, check out the [Garbage Collector design document]().
To learn more, check out the [Garbage Collector design document](garbage-collection.md).
## The Concept of "Managed Code"