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.

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

Epic: implement flow-sensitive bounds declarations #1207

Open
dtarditi opened this issue Jul 11, 2023 · 0 comments
Open

Epic: implement flow-sensitive bounds declarations #1207

dtarditi opened this issue Jul 11, 2023 · 0 comments
Assignees

Comments

@dtarditi
Copy link
Member

dtarditi commented Jul 11, 2023

The bounds widening for pointers to null-terminated arrays relies on flow-sensitive bounds declarations for widening bounds using strlen. Currently the bounds widening is unsound because the flow-sensitive bounds declarations are not checked or used. We should implement flow-sensitive bounds checking. The implementation can be done in 4 stages:

@dtarditi dtarditi added this to the Checked C v1.0 release milestone Jul 11, 2023
@dtarditi dtarditi self-assigned this Jul 11, 2023
@dtarditi dtarditi changed the title Epic: implement flow-sensitive bounds checking Epic: implement flow-sensitive bounds declarations Jul 11, 2023
@dtarditi dtarditi moved this to In Progress in Checked C Board Jul 11, 2023
dtarditi added a commit that referenced this issue Sep 28, 2024
These changes fix the Windows CI runs when using GitHub's "windows-latest" runners. 
- Disable 2 failing clang tests for CUDA features.   There is a Windows configuration specific issue that I don't want to spend time tracking down.  The tests work fine on my Windows machine and break on GitHub's CI runner.
- GitHub's Windows latest no longer includes Python's distutil package for Python 3.10, even though it wasn't removed until Python 3.12.  Switch over to the recommended shutil package. 
- Work around a bug in shutil for Python 3.10 on Windows where it sometimes ignores the shell variable for executable file extensions.  This causes the `which` function to not find `clang`, because the actual file name on Windows is `clang.exe`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

No branches or pull requests

1 participant