Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Submit feedback
    • Contribute to GitLab
  • Sign in
M
mu-impl-fast
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 40
    • Issues 40
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 1
    • Merge Requests 1
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Commits
  • Issue Boards
  • mu
  • mu-impl-fast
  • Issues
  • #33

Closed
Open
Opened Jun 07, 2017 by Yi Lin@u4776528
  • Report abuse
  • New issue
Report abuse New issue

Rework on pin/unpin

Current PIN/UNPIN directly get translated into a runtime call into GC to pin/unpin the object, which simply push/remove the object reference to/from a root set (synchronisation required). This is inefficient, and also the behaviour is different from the spec (in which you need unpin operations to match every pin operation).

This will need rework, probably along with #12 (closed) . And it is also related with mu-spec#7, which proposes to separate immovability and immortal semantics of PIN instruction.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
2
Labels
bug spec coverage
Assign labels
  • View project labels
Reference: mu/mu-impl-fast#33