Lines Matching full:interpreter
82 <h2>Interpreter</h2>
86 The portable interpreter is largely contained within a single C function,
91 The fast interpreter uses hand-coded assembly fragments. If none are
93 interpreter out of C "stubs". The resulting "all stubs" interpreter is
94 quite a bit slower than the portable interpreter, making "fast" something
97 The fast interpreter is enabled by default. On platforms without native
98 support, you may want to switch to the portable interpreter. This can
105 interpreter enabled.
109 <h3>Mterp Interpreter Structure</h3>
113 interpreter core in assembly language, using architecture-specific
116 The simplest way to implement an interpreter is to have a large "switch"
117 statement. After each instruction is handled, the interpreter returns to
123 This makes the interpreter a little larger overall, but you get to avoid
146 The interpreter sources live in <code>dalvik/vm/mterp</code>. If you
192 At this point you have an "all stubs" interpreter. You can see how it
259 with the basic set defined by the portable interpreter.
286 assembly interpreter. You may find it saves a little time to examine
293 <h3>Interpreter Switching</h3>
296 The Dalvik VM actually includes a third interpreter implementation: the debug
297 interpreter. This is a variation of the portable interpreter that includes
305 "portable" interpreter.
309 will need to return a boolean that indicates whether the interpreter is
322 useful during interpreter development is <code>003-omnibus-opcodes</code>,
335 one Dalvik interpreter or the other.
349 your interpreter. The easiest way to do this is to simply connect a
