Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Change type compatibility rules for functions with bounds-safe interfaces. #84

Closed
dtarditi opened this issue Nov 22, 2016 · 1 comment
Closed

Change type compatibility rules for functions with bounds-safe interfaces. #84

dtarditi opened this issue Nov 22, 2016 · 1 comment
Milestone
Sprint 11

Comments

@dtarditi
Copy link
Contributor

We need to allow a bounds declaration to be omitted on a parameter with unchecked pointer type in one function type and to appear on corresponding parameter in the other type. A similar rule needs to apply to function returns.
@dtarditi dtarditi added this to the Sprint 11 milestone Nov 22, 2016
@dtarditi
Copy link
Contributor Author

Completed as part of pull request #91.

dopelsunce pushed a commit to dopelsunce/checkedc-clang that referenced this issue Sep 28, 2020
@dtarditi
Update error messages for bounds mismatches. (microsoft#84)
4eaa515 
The clang error message for bounds mismatches when functions were redeclared was "mismatched type", which was not helpful.   We've updated the Checked C version of clang to produce better error messages for mismatched bound.   This updates the error messages in the tests.   Also rename some functions from to begin with f instead of fn.
@secure-sw-dev-bot secure-sw-dev-bot mentioned this issue Jan 16, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
Sprint 11
Development

No branches or pull requests
1 participant
@dtarditi