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.

To protect your data, the CISO officer has suggested users to enable 2FA as soon as possible.
Currently 2.7% of users enabled 2FA.

Open
Created 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.