什么是/ optimize C＃编译器密钥用于？

Question

Is there a full list of optimizations done by the /optimize C# compiler key available anywhere?

EDIT: Why is it disabled by default? Is it worth using in a real-world app? -- it is disabled by default only in Debug configuration and Enabled in Release.

Answer 1

Scott Hanselman has a blog post that shows a few examples of what /optimize (which is enabled in Release Builds) does.

As a summary: /optimize does many things with no exact number or definition given, but one of the more visible are method inlining (If you have a Method A() which calls B() which calls C() which calls D(), the compiler may "skip" B and C and go from A to D directly), which may cause a "weird" callstack in the Release build.

Answer 2

It is disabled by default for debug builds. For Release builds it is enabled.

It is definitely worth enabling this switch as the compiler makes lots of tweaks and optimizations depending on the kind of code you have. For eg: Skipping redundant initializations, comparisons that never change etc.

Note: You might have some difficulty debugging if your turn on optimization as the code you have and the IL code that is generated may not match. This is the reason it is turned on only for Release builds.

Answer 3

Quoted from the MSDN page :

The /optimize option enables or disables optimizations performed by the compiler to make your output file smaller, faster, and more efficient.

In other words, it does exactly what you think it would - optimises the compiled CIL (Common Intermediate Language) code that gets executed by the .NET VM. I wouldn't worry about what the specific optimisations are - suffice to say that they are many, and probably quite complex in some cases. If you are really interested in what sort of things it does, you could probably investigate the Mono C# Compiler (I doubt the details about the MS C# one are public).

The reason optimisation is disabled by default for Debug configurations is that it makes certain debugging features impossible. A few notable ones:

• Perhaps most crucially, the Edit and Continue feature is disabled - ie no modifying code during execution.
• Breaking execution often means the wrong line of code is highlighted (usually the one after the expected one).
• Unused local variables aren't actually assigned or even declared.

Really, the default options for optimisation never ought to be changed. Having the option off for debugging is highly useful, while having it on for Release mode is equally wise.