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
The Par framework is initialized with an int32 array and a base address within that int32 array that it can use for its metadata. It then computes offsets from that base address to use for its internal variables. It would be better if it were to create a new array from the underlying buffer starting at that base address, and clamped to MasterPar.NUMINTS in length. Its variable offsets would then always start at 0, and we'd get range checking on both the master and the workers.
The text was updated successfully, but these errors were encountered:
The Par framework is initialized with an int32 array and a base address within that int32 array that it can use for its metadata. It then computes offsets from that base address to use for its internal variables. It would be better if it were to create a new array from the underlying buffer starting at that base address, and clamped to MasterPar.NUMINTS in length. Its variable offsets would then always start at 0, and we'd get range checking on both the master and the workers.
The text was updated successfully, but these errors were encountered: