Stack Trace for logging in .NET

家住魔仙堡 提交于 2019-12-05 09:37:22

Yes, there are some rules but they are heuristics used by the JIT compiler and these heuristics can change at a moment's notice.

  1. Virtual methods cannot be inlined.
  2. Interface methods, on the other hand, may be inlined although I am not 100% sure whether or not this would collapse the stack trace.
  3. Static methods and non-virtual instance methods can certainly be inlined.
  4. Inlining may cross namespaces (of course) and assemblies (not so obvious) because it happens at run-time, when the JIT compiles the method call.
  5. "Heavy" methods will not be inlined. This depends on the definition of "heavy", and is part of the heuristics the JIT applies.

Some of the heuristics for "heavy" that I'm aware of:

  • Methods which use exception handling (i.e. try-catch or try-finally blocks) are not inlined.
  • Methods with large code (~32 IL bytes but I may be remembering this wrong) are not inlined.
  • Methods with loops are not inlined (unless the loop can be completely unrolled or eliminated).

The heuristics are all implementation details of the jitter, meaning that they aren't officially documented and are presumably subject to change at any time.

Having said that, here are some articles that you might find interesting (although some of them are a bit long-in-the-tooth now):

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!