Internally, bytecode interpreter (i.e. vm_exec() function found in the bytecode.dl dynamic library) uses the following register assignments:
er0 virtual register R0 (accumulator/pointer for indirect loads),
er1 virtual register R1 (aux data register/pointer for indirect saves),
er2 'this' for the object/actor/struct being processed,
er3 scratch register,
er4 table of extension functions (caller-supplied),
er5 table of built-in opcodes,
er6 p-code instruction pointer (static data/code space),
er7 stack pointer.
See also:
| file: /Techref/cybiko/bc/regs.htm, 0KB, , updated: 2008/6/12 19:30, local time: 2012/2/10 03:05,
38.107.179.231:LOG IN |
| ©2012 These pages are served without commercial sponsorship. (No popup ads, etc...).Bandwidth abuse increases hosting cost forcing sponsorship or shutdown. This server aggressively defends against automated copying for any reason including offline viewing, duplication, etc... Please respect this requirement and DO NOT RIP THIS SITE. Questions? <A HREF="http://www.piclist.com/techref/cybiko/bc/regs.htm"> Cybiko Bytecode Interpreter </A> |
| Did you find what you needed? |
|
The PICList shop now offers mugs, steins and... T-Shirts!!! |
|
The only consistant, simple to use yet powerful development environment. It simulates real-world devices via virtual component "plugins" (LED,LCD,key,motor,TV,etc) in real time, has a syntax highlighting editor, macro assembler and disassembler. Regular updates and third-party plugins keep this software ahead of any other PIC IDE. |
.