Scpptool – a tool to enforce a memory and data race safe subset of C++
scpptool is a command line tool that enforces memory and data race safety in C++ by analyzing code for unsafe areas, compatible with Clang and providing extensive documentation and resources.
Read original article
scpptool is a command line tool designed to enforce a memory and data race safe subset of C++ in conjunction with the SaferCPlusPlus library. It analyzes C++ files to identify unsafe code areas, ensuring compliance with memory and data race safety standards. The tool is compatible with the Clang compiler and requires Clang+LLVM libraries. It features checks for memory safety, prohibiting null values for raw pointers and treating standard library containers as unsafe. Its flow-insensitive analysis allows for scalable safety checks that are not dependent on program flow. Users can also suppress specific checks locally using directives. The tool can be built on Ubuntu Linux, with detailed instructions provided in the repository. Usage is straightforward, allowing users to specify source files and compiler options easily. The repository includes examples of safe code and comprehensive documentation on using the tool, including annotations for lifetimes and safe pointer management. Additional resources, such as quick intro videos and transcripts, are available for further insights into the tool's functionality.
- scpptool enforces a safe subset of C++ for memory and data race safety.
- It is compatible with the Clang compiler and requires Clang+LLVM libraries.
- The tool allows local suppression of specific safety checks in the code.
- Detailed documentation and examples are provided in the repository.
- Additional resources include videos and transcripts for better understanding.
Related
New Features in C++26
The ISO released new C++ standards on a three-year cycle, with C++26 proposals open until January 2025. Updates include hazard pointers, user-space RCU support, debugging headers, and template enhancements for improved functionality.
Cppfront: Midsummer Update
Herb Sutter updated on cppfront, an experimental C++ project enhancing safety and simplicity. Recent releases include new syntax features and improvements, with plans for regular updates and community involvement.
ICPP – Running C++ in anywhere like a script
ICPP is a tool that enables execution of C++ code similarly to scripting languages, supporting Standard C++23, remote execution, hot-loading, and module management, enhancing developer productivity and flexibility.
Safer C++
Alex Gaynor advocates transitioning from C/C++ to memory-safe languages in security-critical contexts, proposing improvements in C++ safety through bounds checking, smart pointers, and a dual strategy for teams.
Safer C++
Alex Gaynor advocates transitioning from C/C++ to memory-safe languages in security-critical contexts, proposing improvements in C++ safety while acknowledging challenges and recommending a dual strategy for enhancement and migration.
4 comments mse::rsv::TXSLTACSSSXSTERandomAccessIterator
> The "CSSSXSTE" part of the typenames stands for "Contiguous Sequence, Static Structure, XSLTA, Type-Erased".
But it nowhere defines XSLTA. With some help from ChatGPT, I can guess that "XS" stands for "execution scope" (since the readme talks a lot about execution scopes), and "LTA" probably stands for "lifetime annotated" (since one part says that "rsv::TXSLTAOwnerPointer<> is a 'lifetime annotated' version of TXScopeOwnerPointer<>").
But what about the namespaces, "mse" and "rsv"? I can find nothing to explain what those might stand for.
Anyway.
I really like the idea of this project. There are contexts where I cannot use Rust and would love to have a way equivalent safety guarantees in C++. Even at the cost of rewriting the code. And even at the cost of ugly code, because there will be some necessary ugliness when retrofitting lifetimes into C++'s existing syntax and semantics.
But "TXSLTACSSSXSTERandomAccessIterator" is unnecessary ugliness. There are better ways to get ideas across than acronym soup.
There are some other practical issues with the project, such as inconsistent licensing annotations, and the fact that it seems to depend on specific Clang versions (and thus will probably bitrot if it stops being maintained).
Still, it seems promising and I may use it someday.
Related
New Features in C++26
The ISO released new C++ standards on a three-year cycle, with C++26 proposals open until January 2025. Updates include hazard pointers, user-space RCU support, debugging headers, and template enhancements for improved functionality.
Cppfront: Midsummer Update
Herb Sutter updated on cppfront, an experimental C++ project enhancing safety and simplicity. Recent releases include new syntax features and improvements, with plans for regular updates and community involvement.
ICPP – Running C++ in anywhere like a script
ICPP is a tool that enables execution of C++ code similarly to scripting languages, supporting Standard C++23, remote execution, hot-loading, and module management, enhancing developer productivity and flexibility.
Safer C++
Alex Gaynor advocates transitioning from C/C++ to memory-safe languages in security-critical contexts, proposing improvements in C++ safety through bounds checking, smart pointers, and a dual strategy for teams.
Safer C++
Alex Gaynor advocates transitioning from C/C++ to memory-safe languages in security-critical contexts, proposing improvements in C++ safety while acknowledging challenges and recommending a dual strategy for enhancement and migration.