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
There were 3 issues with the handling of variables used in the declared bounds
of an nt_array_ptr:
Bounds variables were being determined only for nt_array_ptrs declared in
the current block. As a result, if a variable is killed in a block then the
widened bounds in the successor blocks could not be killed. This is fixed by
storing the bounds variables along with the nt_array_ptrs for the entire
function instead of per block.
Bounds variables for function parameters were not getting determined
correctly. This is fixed by uniforming the logic to determine bounds
variables for function parameters and local variables.
Bounds declared as CountBoundsExpr were not being handled. This is fixed by
reading the NormalizedBounds instead of invoking ExpandBoundsToRange.
This issue was copied from checkedc/checkedc-clang#898
There were 3 issues with the handling of variables used in the declared bounds
of an
nt_array_ptr
:Bounds variables were being determined only for
nt_array_ptr
s declared inthe current block. As a result, if a variable is killed in a block then the
widened bounds in the successor blocks could not be killed. This is fixed by
storing the bounds variables along with the
nt_array_ptr
s for the entirefunction instead of per block.
Bounds variables for function parameters were not getting determined
correctly. This is fixed by uniforming the logic to determine bounds
variables for function parameters and local variables.
Bounds declared as
CountBoundsExpr
were not being handled. This is fixed byreading the
NormalizedBounds
instead of invokingExpandBoundsToRange
.Also performed minor NFC code cleanups.
Fixes checkedc/checkedc-clang#895
The text was updated successfully, but these errors were encountered: