Why a standalone preprocessor
Preprocessing looks like nothing more than “macro expansion”, but real projects turn it into the intersection of diagnostics, dependencies, PCH, character sets, macro state, and build caching. Only by splitting it into a standalone layer can it be observed, tested, and optimized on its own.
CrucibleCpp's goal is not to rewrite the compiler, but to turn translation phases 1–4 into a component with clear boundaries and behavior that can be compared directly.
Design principles
- Behavior is benchmarked against GCC. Not “looks reasonable” — it is verified against real GCC.
- Every positive case must be compiled and run. A successful preprocessing run doesn't mean the output is usable.
- Versions are not mixed. The target GCC profile, headers, and compile commands must all match.
- Limitations are not hidden. Unsupported capabilities are spelled out; “should work” is not a substitute for verification.
- Windows x64 first. Make one target trustworthy first, then talk about cross-platform.
Current status
- Version: V3.0.1
- Platform: Windows x64 / UCRT64
- Target GCC: 13.3 / 14.3 / 15.2
- Standards: C++11 / 14 / 17 / 20
- Tests: three suites at 65/65
- License: CC BY-NC 4.0
TomatoOyster
An independent developer focused on C++ toolchains, build systems, and verifiable engineering infrastructure.
CrucibleCpp
A standalone C++ preprocessor for Windows x64, intended to replace the g++ -E step in the build pipeline.
GitHub
Questions, suggestions, and release information are tracked through GitHub Issues / Releases.
Submit an Issue →