In economical JIT compilation first the ,net application will be complied by the language compiler into MSIL code and will be permanently saved in a file with extension either exe or dll .While executing the application MSIL code will be loaded as it is into memory by attaching a stab to every method and when you call a method for the first time.
Then the stub attached to the method will be redirect the control to JIT compiler that will compile only that particular method to CPU native code and execute it.But when you call the same method again the stub attached to the method will be directly control to memory CPU method native code OS readily available
As MSIL code will not be compiled to CPU native code while loading the app loading application will a fast in the someway during executing also as only one method you call is compiled execution will also be fast
Then the stub attached to the method will be redirect the control to JIT compiler that will compile only that particular method to CPU native code and execute it.But when you call the same method again the stub attached to the method will be directly control to memory CPU method native code OS readily available
As MSIL code will not be compiled to CPU native code while loading the app loading application will a fast in the someway during executing also as only one method you call is compiled execution will also be fast
No comments:
Post a Comment