Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in
G
general-issue-tracker
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 47
    • Issues 47
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • mu
  • general-issue-tracker
  • Issues
  • #8

Closed
Open
Opened Aug 27, 2014 by John Zhang@u51577796 of 6 tasks completed6/6 tasks
  • Report abuse
  • New issue
Report abuse New issue

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.

Assignee
Assign to
spec-2
Milestone
spec-2
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: mu/general-issue-tracker#8