[parrot/parrot] f977aa: Initial step towards Lorito M0 opcodes as dynops
noreply at github.com
noreply at github.com
Sat Dec 11 10:20:02 UTC 2010
Branch: refs/heads/lorito
Home: https://github.com/parrot/parrot
Commit: f977aa9b116ba174a5a90f8c91c22c779f182bb2
https://github.com/parrot/parrot/commit/f977aa9b116ba174a5a90f8c91c22c779f182bb2
Author: Jonathan "Duke" Leto <jonathan at leto.net>
Date: 2010-12-11 (Sat, 11 Dec 2010)
Changed paths:
M MANIFEST
M MANIFEST.SKIP
M src/dynoplibs/Defines.in
M src/dynoplibs/README
M src/dynoplibs/Rules.in
A src/dynoplibs/lorito.ops
A t/dynoplibs/lorito.t
Log Message:
-----------
Initial step towards Lorito M0 opcodes as dynops
This is a prototype of Lorito M0 opcodes written in terms of dynamically
loadable opcodes. The purpose of this prototype is to see if current
Parrot opcodes can be written in terms of some basic M0 opcodes.
Commit: 99c65f48468b643252159c0b15a8691c62de6358
https://github.com/parrot/parrot/commit/99c65f48468b643252159c0b15a8691c62de6358
Author: Jonathan "Duke" Leto <jonathan at leto.net>
Date: 2010-12-11 (Sat, 11 Dec 2010)
Changed paths:
M src/dynoplibs/lorito.ops
M t/dynoplibs/lorito.t
Log Message:
-----------
[t] Context op should return a single PMC
Currently dies with:
attempt to access code outside of current code segment
because the program counter is wrong.
More information about the parrot-commits
mailing list