Skip to content

GitLab

WARNING! Access to this system is limited to authorised users only.
Unauthorised users may be subject to prosecution.
Unauthorised access to this system is a criminal offence under Australian law (Federal Crimes Act 1914 Part VIA)
It is a criminal offence to:
(1) Obtain access to data without authority. -Penalty 2 years imprisonment.
(2) Damage, delete, alter or insert data without authority. -Penalty 10 years imprisonment.
User activity is monitored and recorded. Anyone using this system expressly consents to such monitoring and recording.

Closed
Created by John Zhang@u5157779Developer6 of 6 tasks completed6/6 tasks

Next milestone

Created by: wks

As we already found many problems in the current µVM design, many changes can be done to improve it. Here is a list of issues to be addressed in the next µVM specification.

  • #6 #10 (closed) : More instructions can result in abnormal control flows. This should be reflected in the instruction set.
    • Stick to the standard control flow graph, not factored control flow graph.
  • #4 (closed) : Use C++11 memory model.
  • #7 (closed) : Update the swap-stack API.
  • #5 (closed) : Update the OSR API.
  • #9 : Support vector instructions.
  • Provide mechanisms (futex) to support blocking locks and other thread synchronisation primitives.

In case there are someone who wants to play with the reference implementation, the current implementation will be branched and the current specification will be forked into another repository.