Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • M mu-spec
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 16
    • Issues 16
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • mumu
  • mu-spec
  • Issues
  • #3
Closed
Open
Issue created Apr 05, 2017 by Yi Lin@u4776528Owner

Add semantics about GC finaliser to spec

The proposal is from general-issue-tracker#27 by Kunshan Wang.

The proposal suggests two common instructions, @uvm.gc.prevent_death_once and @uvm.gc.next_object_to_finalise.

  • @uvm.gc.prevent_death_once marks an object as finalisable. When GC finds the object dead, it put the object to a finalisable object queue.
  • @uvm.gc.next_object_to_finalise will pop an object reference from the queue.

These instructions allow client to create a finaliser thread (running Mu code). e5848b32 captures the idea and put them into the spec.

Assignee
Assign to
Time tracking