So these past days I was kind of bored and also I wanted to prove to myself that I can take a serious software project and the understand it. I heard so many things about the CLR like it was some kind of alien technology that no one could understand. I saw that it as a challenge and decided to see if it's really like that.
And the rumors were true in a way. The CLR is a marvel of software engineering. It is actually made out of multiple systems with one central system that glues them together. That central system is called the "Execution Engine". I think it's what controls and manages the execution of the program. It is for example responsible for stopping the execution of the program when the garbage collector starts to do it's job.
Actually the garbage collector sends a command to the execution engine to stop the execution of the program. Yes, the garbage collector is another system just like the execution engine. It is actually pretty interesting to see how the garbage collector actually works. The thing is that the code is compiled to native code when the program is executed. And the garbage collector has to somehow make sense of that compiled code in x86 assembly. I think it accesses the variables and objects through a high level interface that takes that compiled x86 code and translates it into something that the garbage collector can use. For example, local references stored on the stack need to be somehow accessed by the GC but it's all compiled code and you somehow need to know where inside the original IL code the execution stopped so you can see what references are available. Those references are used as roots to keep objects alive.
Not only that but I think the execution engine is also responsible for probing variables which is used by the debugger. I saw that there are some structures, C++ structures that tells the location of some variables. I think these are used to show in the locals window in Visual Studio the variables visible in the current scope.
I also think that the execution engine is responsible for debugging too. It can stop the execution of the program or let the program run until a certain point in the code is reached.
Another system inside the CLR is the jit compiler. I think all the IL instructions inside a method are added inside a tree, actually a GenTree that is then modified for specific optimizations. One of these optimizations that I noticed is "folding". I think this means that if we add some constant values inside the code, then before compiling those IL instructions to native code, the constant values are added together and replaced with that result. For example if you have inside the code an expression like "x+4+5" it will get transformed into "x+9".
After all the optimizations are done, I think that tree is traversed by the compiler and x86 code is generated.
And the rumors were true in a way. The CLR is a marvel of software engineering. It is actually made out of multiple systems with one central system that glues them together. That central system is called the "Execution Engine". I think it's what controls and manages the execution of the program. It is for example responsible for stopping the execution of the program when the garbage collector starts to do it's job.
Actually the garbage collector sends a command to the execution engine to stop the execution of the program. Yes, the garbage collector is another system just like the execution engine. It is actually pretty interesting to see how the garbage collector actually works. The thing is that the code is compiled to native code when the program is executed. And the garbage collector has to somehow make sense of that compiled code in x86 assembly. I think it accesses the variables and objects through a high level interface that takes that compiled x86 code and translates it into something that the garbage collector can use. For example, local references stored on the stack need to be somehow accessed by the GC but it's all compiled code and you somehow need to know where inside the original IL code the execution stopped so you can see what references are available. Those references are used as roots to keep objects alive.
Not only that but I think the execution engine is also responsible for probing variables which is used by the debugger. I saw that there are some structures, C++ structures that tells the location of some variables. I think these are used to show in the locals window in Visual Studio the variables visible in the current scope.
I also think that the execution engine is responsible for debugging too. It can stop the execution of the program or let the program run until a certain point in the code is reached.
Another system inside the CLR is the jit compiler. I think all the IL instructions inside a method are added inside a tree, actually a GenTree that is then modified for specific optimizations. One of these optimizations that I noticed is "folding". I think this means that if we add some constant values inside the code, then before compiling those IL instructions to native code, the constant values are added together and replaced with that result. For example if you have inside the code an expression like "x+4+5" it will get transformed into "x+9".
After all the optimizations are done, I think that tree is traversed by the compiler and x86 code is generated.
Comments
Post a Comment