您要查找的是不是：
- The count of methods generated by the JIT compiler. 由JIT编译器生成的方法的计数。
- The standard JIT compiler runs on demand. 标准JIT编译器上运行的需求。
- The number of bytes in use by the JIT compiler's heap. 由JIT编译器的堆使用的字节数。
- Reducing the length of these methods can make them more amenable to optimization by a JIT compiler. 而缩短这些方法的长度有助于使JIT编译器更易于优化它们。
- The total time, in milliseconds, spent discarding methods generated by the JIT compiler. 丢弃由JIT编译器生成的方法所花的总时间(以毫秒为单位)。
- At runtime, the JIT compiler links the client calls to the component entry points. 在运行时,JIT编译器将客户端的调用连接到组件的入口点。
- In fact, the C# compiler does not provide any hints to the JIT compiler regarding inlining. 事实上，C%23编译器，没有给JIT编译器任何提示要求考虑内联。
- The function has not yet been JIT compiled. 尚未编译此函式。
- Fewer control branches inside functions make it easier for the JIT compiler to enregister variables. 方法内部更少的控制分支使得JIT编译器为寄存器注册变量更容易。
- NET runtime invokes the JIT compiler to translate the IL generated by the C# compiler into machine code.. Net运行时调用JIT编译器将C%23编译器生成的IL转换成机器代码。
- The JIT compiler understands your need for both efficiency and elegance, so it inlines the property accessor. JIT编译器了解你的对于效率与优雅的需求，因此它对属性访问符进行了内联。
- The simplicity of the control flow also affects how well the JIT compiler can enregister variables. 这个简单的控制流程同样会影响JIT编译对变量注册的好坏。
- If the JIT compiler inlines the property accessor, it must JIT that code when the containing method is called. 如果JIT编译器内联了该属性访问符，那么，当包含的方法被调用时，就必须JIT那些代码。
- Creating fewer local variables gives the JIT compiler a better chance to find the best candidates for enregistration. 创建更少的局部变量给JIT提供了更好的机会寻找最合适寄存器候选对象。
- The JIT compiler generates machine code for each method (or group of methods, when inlining is involved), as needed. JIT编译器为每个方法(或者，如果涉及到内联的话，就是一组方法)生成必需的机器码。
- The JIT compiler can perform more efficient inlining inside an assembly than across assembly boundaries. 在一个程序集内部与跨程序集相比较，JIT编译器可以高效的进行内联。
- Smaller and simpler functions make it easier for the JIT compiler to support enregistration. 小而简单的方法使得JIT编译器支持可注册更容易。
- Because the JIT compiler uses the same value-type-specific server code in all further encounters, there is no code bloating. 因为JIT编译器在以后的所有场合中都将使用相同的值类型特定的服务器代码,所以不存在代码膨胀问题。
- JIT compilation is significantly different from interpreting code. JIT编译与解释代码有很大的不同。
- This counter is updated at the end of every JIT compilation phase. 在每一JIT编译阶段的结尾更新此计数器。
