简介：adventures in windows debugging and reverse engineering.

原站：http://www.nynaeve.net

指数：

“Nynaeve”的内容更新

累计：27 篇（自 2009-11-27 起）

更新：约12篇/年，最后更新542 天前

Nynaeve

NWScript JIT engine: Wrap-up (for now)

yesterday, i provided a brief performance overview of the msil jit backend versus my implementation of an interpretive vm for various workloads.today, i’ll mostly pontificate on conclusions from the jit project. it has certainly been an interesting foray into .net, program analysis, and code generation; the jit engine is actually my first non-trivial .... (306 天前)

http://inezha.com/w/1n9kiur

Nynaeve

NWScript JIT engine: Performance considerations

last time, we learned how save_states are supported by the msil jit backend. this time, we’ll touch on everybody’s favorite topic — performance.after all, the whole point of the jit project is to improve performance of scripts; there wouldn’t be much point in using it over the interpretive vm if it wasn’t faster.so, just how much faster is the msi... (306 天前)

http://inezha.com/w/pvxc1ud

Nynaeve

NWScript JIT engine: MSIL backend support for SAVE_S

yesterday, i described how the fast action call mechanism improves action call performance for jit’d programs. for today’s nwscript adventure, let’s dig into how save_state operations (script situations) are supported in the msil jit backend.as you may recall, save_state operations (codified by i_save_state in the ir instruction set and op_store_stat... (306 天前)

http://inezha.com/w/35eq7u9

Nynaeve

NWScript JIT engine: JIT intrinsics, and JIT’d acti

previously, i explained how the ‘fast’ action service call interface worked — and why it doesn’t always live up to its namesake.this time, we’ll examine the no-holds-barred, non-verifiable direct fast action call path. this action service call mechanism is designed for maximum performance at the expense of type-safe, verifiable il; as you’ll see, ... (306 天前)

http://inezha.com/w/6w9b6uu

Nynaeve

NWScript JIT engine: JIT intrinsics, and JIT’d acti

yesterday, we learned how the standard action service call path operates in the msil jit backend for the nwscript jit engine. this time, we’ll examine the ‘fast’ action service call path.as i alluded to last time, the fast action service call path attempts to cut down on the overhead of making multiple managed/native transitions for each action servi... (306 天前)

http://inezha.com/w/fpxhlut

Nynaeve

NWScript JIT engine: JIT intrinsics, and JIT’d acti

last time, i outlined the general usage of the jit intrinsics emitted by the msil backend for the nwscript jit engine, and how they relate to action service calls. today, let’s take a closer at how an action service handler is actually called in nwscript in the wild.the msil backend currently supports three action call mechanisms (the ’standard’ intr... (306 天前)

http://inezha.com/w/aidd5u0

Nynaeve

NWScript JIT engine: JIT intrinsics, and JIT’d acti

previously, i demonstrated how a simple nwscript subroutine could be translated into msil, and then to native instructions by the clr jit. we still have a large piece of functionality to cover, however, which is calling action service handlers (extension points) from jit’d code. in order to understand how action service handlers work, we need to delve i... (306 天前)

http://inezha.com/w/5gm1i5o

订阅者 ( 1 )

相关订阅源