请问C＃编译器/优化命令行选项影响抖动？ [英] Does C# compiler /optimize command line option affect JITter?

问题描述

的

我一直在阅读埃里克利珀的有关C＃编译器的/优化命令行选项文章。本文介绍了编译器执行什么样的优化。但是，如果此选项会影响JIT优化以及尚不清楚给我。它不是不可想象的，这个选项将使编译器产生的一些元数据，即抖动能够理解改变优化模式。有没有可以确认或否则，如果该选项确实影响抖动的内容？

解决方案

时有可以确认或否则，如果该选项确实影响抖动的内容？

据杰弗里·里希特在他的CLR通过C＃的书，第三版（第1章，第13页），它的作用。在 /优化+ 开关将导致优化的C＃的IL代码，以及由JIT编译器生成的本地代码。至于的如何的它实际上这样做，我不知道。我的胡乱猜测是，它可能有一些做的的 CorDebugJITCompilerFlags 枚举。

I've been reading Eric Lippert's article about the /optimize command line option of the C# compiler. The article describes what kind of optimizations the compiler performs. However it remains unclear to me if this option affects JIT optimization as well. It is not unthinkable, that this option would make the compiler to emit some metadata, that jitter can understand to change "optimization mode". Is there any reference that can confirm or otherwise if this option does indeed affect JITter?

解决方案

Is there any reference that can confirm or otherwise if this option does indeed affect JITter?

According to Jeffrey Richter in his CLR via C# book, 3rd edition (chapter 1, page 13), it does. The /optimize+ switch will result in optimizations for C# IL code, as well as the native code generated by the JIT compiler. As to how it actually does that, I'm not sure. My wild guess is that it might have something to do with the CorDebugJITCompilerFlags enumeration.

这篇关于请问C＃编译器/优化命令行选项影响抖动？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！