Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • M mu-impl-fast
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 40
    • Issues 40
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar

GitLab will be upgraded on 30 Jan 2023 from 2.00 pm (AEDT) to 3.00 pm (AEDT). During the update, GitLab and Mattermost services will not be available. If you have any concerns with this, please talk to us at N110 (b) CSIT building.

  • mu
  • mu-impl-fast
  • Issues
  • #15

Closed
Open
Created Mar 16, 2017 by Yi Lin@u4776528Owner2 of 3 tasks completed2/3 tasks

Removing unnecessary use of lock/`Option` for IR data structures

This issue tracks unnecessary uses of locks in Zebu. The old Mu spec requires mutation on the IR, for example, creating a IR node, then adding a name to it. Thus either locks or Option<T> are introduced to allow mutation. The new spec makes the IR almost (if not completely) immutable. It is possible to remove most of the locks.

Some rewrite compilation passes try to mutate on IR nodes as well. However, we can always copy and update instead of mutating.

Lock:

  • name field in MuEntityHeader
  • ops field in Instruction

Option<T>:

  • Most of the Option uses in ir.rs
Assignee
Assign to
Time tracking