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
When programmers redeclare functions with parameters or returns that have bounds declarations, we check that the bounds declarations are syntactically equal (modulo variable names). We need to make sure that the relative alignment clause is included in the check.
This work item has two parts:
Make sure that the relative alignment clause is included in the check of equality of bounds. This is implement in lib\AST\StmtProfile.cpp. The function for Visit*BoundsExpr need to be extend to include the relative alignment information.
Add tests to the Checked C repo in tests\typechecking\redeclarations.c for this functionality.
The text was updated successfully, but these errors were encountered:
By default, checked scopes will include compile-time checks to prevent type
confusion. The checks will restrict pointer casts, for example. If a
programmer wants only checks for bounds safety, a programmer can modify a
checked scope using the _Bounds_only modifier:
checked bounds_only { ... }
This change adds tests of checked scopes with the new bounds_only modifier.
We haven't implemented the restrictions on pointer casts yet, so the tests
check only that checked scopes with bounds_only modifiers implement the same
restrictions that regular checked scopes currently do.
The change parameterizes checked_scope_basic.c by a #define that adds
a scope modifier optionally. We create a dummy file to compile the alternate
version of the file.
When programmers redeclare functions with parameters or returns that have bounds declarations, we check that the bounds declarations are syntactically equal (modulo variable names). We need to make sure that the relative alignment clause is included in the check.
This work item has two parts:
The text was updated successfully, but these errors were encountered: