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
Report abuse

add lowtagref

This materialised the proposal of low tagged reference (as lowtagref) in Issue #2. It is a more lightweight tagged reference than tagref64. GHC-Mu is a potential user of this type.

I am not sure about two things, please leave comments or make edits if necessary:

  1. Is lowtagref optional? (tagref64 is)
  2. Should we have a fixed tag length (I assume a fixed int<3> tag when I draft the part)? An alternative is that we leave this as implementation dependent, which may be 3/4/5. I guess 3 bits tagging is reasonable as it is the default alignment for a reference type.

As for implementation, it requires GC to distinguish non-ref, ref, tagref64 and lowtagref for each struct field. But as we already need to distinguish the former 3, this doesn't add space overhead for object metadata.