I\'m continuing my work on my C# compiler for my Compilers Class. At the moment I\'m nearly finished with the chapters on Compiler Optimizations in my textbook.
F
David Notario has a few posts on his blog (you can start here, and then walk the history), but they are rather sketchy.
I can imagine there being a number of optimizations that are unique to JIT; specifically, any optimization that depends on the environment/context that the application runs in. (Note, all the following are hypothetical, I do not know for sure, which or if any of these are actually performed)
Most boring: the JIT can optimize depending on 32-bit/64-bit underlying OS, or even potentially depending on the exact processor architecture.
Not applicable: More interesting: the JIT could optimize out anything that only runs in Debug mode (certain conditional code for example) when the application is not run inside a debug context.
Most interesting: the JIT could optimize out conditional branches in a class that depend only on a readonly
field, because at least theoretically that value will never change during the execution of the class.
Basically I'd imagine that deferring optimizations until JIT would generally be the way to go, because at JIT time there is the most information available about the context the code is actually running in, making more meaningful optimizations possible.
I don't think the C# compiler does any optimizations. The JIT does all the work.