This repo contains a version of clang that is being modified to support Checked C. Checked C extends C with checking to detect or prevent common programming errors such as out-of-bounds memory accesses. The Checked C specification is available at the Checked C repo.
| Configuration | Testing | Status |
|---|---|---|
| Debug X86 Windows | Checked C and clang regression tests | |
| Debug X64 Windows | Checked C and clang regression tests | |
| Debug X64 Linux | Checked C and clang regression tests | |
| Release X64 Linux | Checked C, clang, and LLVM nightly tests |
We updated the LLVM/clang sources that we are using on June 20th, 2017. If you have built your own copy of the compiler, you will need to delete your cmake build directory and re-run cmake after you sync.
Programmers are welcome to ``kick the tires'' on Checked C as it is being implemented. You will have to build your own copy of the compiler for now. The compiler code and tests are in multiple repos.
- Setup and Build describes the organization of the code and tests, how to set up a development machine to build clang, and how to build clang.
- Testing describes how to test the compiler once you have built it.
- The Implementation Notes describe the implementation of Checked C in LLVM\clang.
After you have built the compiler, simply add the -fcheckedc-extension flag to your
command-line to enable the Checked C extension.
We are implementing a subset of the Checked C extension that can be used to add bounds checking to real-world C programs. The implementation roadmap and status are on the Checked C Wiki.
We welcome contributions to the Checked C project. To get involved in the project, see Contributing to Checked C. We have a wish list of possible projects there.
For code contributions, we follow the standard Github workflow. See Contributing to Checked C for more detail. You will need to sign a contributor license agreement before contributing code.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.