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
So, there are sometimes bugs in trans related to allocating stack slots for temporary values, but not properly ensuring that the slots are either always initialized or start off with the drop flag zeroed.
A way we could try to guard for such bugs would be: in debug builds, initialize the drop flag with a non-trivial bit pattern, and then check for that bit pattern when dropping the value.
I strongly suspect a check like this would have helped us track down the cause of #20055 faster.
The text was updated successfully, but these errors were encountered:
So, there are sometimes bugs in trans related to allocating stack slots for temporary values, but not properly ensuring that the slots are either always initialized or start off with the drop flag zeroed.
A way we could try to guard for such bugs would be: in debug builds, initialize the drop flag with a non-trivial bit pattern, and then check for that bit pattern when dropping the value.
I strongly suspect a check like this would have helped us track down the cause of #20055 faster.
The text was updated successfully, but these errors were encountered: