You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently resources have a flag of size "int", meaning 32 or 64 bits. This is pretty large for a 1-bit flag. Ideally, it would be a single bit and then allow the alignment code to ensure that the contents of the resource are properly aligned. After the port to x86_64 is running smoothly this would be a good thing to tackle.
The text was updated successfully, but these errors were encountered:
Since most intrinsics are safe it likely makes sense to explicitly
document why there are a few intrinsics that are not safe. These
intrinsics are all unsafe for the same reason, which is that they're
dealing with a raw pointer that must be valid to load/store memory to.
Note that the are no alignment requirements on any of these intrinsics.
Currently resources have a flag of size "int", meaning 32 or 64 bits. This is pretty large for a 1-bit flag. Ideally, it would be a single bit and then allow the alignment code to ensure that the contents of the resource are properly aligned. After the port to x86_64 is running smoothly this would be a good thing to tackle.
The text was updated successfully, but these errors were encountered: