CRC++ 1.0.1.0
Easy to use and fast C++ CRC library.
|
Easy to use and fast C++ CRC library.
Tired of writing CRC code over and over again? Don't want to include a dozen boost header files just for a little bit of functionality? CRC++ is a portable and extremely lightweight alternative that is incredibly simple, fast, and clean.
CRC++ supports bit-by-bit and byte-by-byte calculation of full and multipart CRCs. The algorithms used are highly optimized and can even be configured to be branchless (as always, be sure to profile your code to choose the most efficient option). CRC++ is a great option for embedded C++ projects with a need for efficiency.
CRC++ consists of a single header file which can be included in any existing C++ application. No libraries, no boost, no mess, no fuss.
Any CRC width is supported - even CRCs larger than 64 bits, provided there is an integer type large enough to contain it. Trying to compute a 57-bit CRC? Got you covered.
Many common CRCs are provided out-of-the-box, such as CRC-32 (used in PKZip and Ethernet), CRC-XMODEM, and CRC-CCITT.
CRC++ will compile with any reasonably compliant C++03 or C++11 compiler. Compiling with C++11 is recommended, as it allows a number of static computations to be performed at compile-time instead of runtime.
All of the CRC++ code is well-documented. Unit tests are included in the repository (g++ Makefile and Visual Studio 2015 projects included). HTML documentation can also be produced via Doxygen (also included in the repository).
CRC++ boasts one of the fastest and most memory efficient generic CRC implementation available. The below table shows performance comparisons across multiple implementations and platforms.
Library | Speed, x64 platform (100 million iterations) | Speed, x86 platform (100 million iterations) |
---|---|---|
CRC++ | 2050 milliseconds | 2200 milliseconds |
boost | 2250 milliseconds | 2000 milliseconds |
pycrc | 2050 milliseconds | 2240 milliseconds |
mhash | 2250 milliseconds | 2400 milliseconds |
Additionally, CRC++ has the most features of any library and the smallest code footprint:
Library | Number of include files | Header-only implemen-tation | Supports byte != 8 bits | Supports arbitrary CRC width | Custom type support | C++11 support | 40+ built-in CRC definitions | Branchless implemen-tation |
---|---|---|---|---|---|---|---|---|
CRC++ | 1 | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
boost | 17 | Yes | Yes | Yes | Yes | Yes | No | No |
pycrc | 2 per CRC algorithm | No | No | No | No | No | No | No |
mhash | 6 | No | Yes | No | No | No | No | No |
Computing a CRC is as simple as the following code:
Multi-part CRCs are also supported:
This will return the same CRC as the first example.
If you need to compute a CRC on an input that is not a multiple of CHAR_BIT
(usually 8 bits), use the CalculateBits()
function instead:
The above examples compute a CRC bit-by-bit. However, CRC++ also supports lookup tables, as the following example demonstrates:
Or, if you prefer using the auto
keyword:
Lookup tables are much faster than computing a CRC bit-by-bit, at the expense of extra memory usage. A lookup table can be reused for as many CRCs as desired until it goes out of scope.
CRC++ can be configured by setting various #define
s before #include
-ing the CRC++ header file:
#define crcpp_uint8
#define crcpp_uint16
#define crcpp_uint32
#define crcpp_uint64
#define crcpp_size
#define CRCPP_USE_NAMESPACE
#define CRCPP_BRANCHLESS
#define CRCPP_USE_CPP11
Define to enables C++11 features (move semantics, constexpr, static_assert, etc.). Not defined by default.#define CRCPP_INCLUDE_ESOTERIC_CRC_DEFINITIONS
Define to include definitions for little-used CRCs. Not defined by default.CRC does not require a build for basic usage; simply include the header file in your project.
Unit tests and documentation can be built manually with the project files provided or automatically with CMake.
To build documentation manually:
To build unit tests manually via Make:
Project files and solutions for Visual Studio 2015, 2017 and 2022 are provided in test/prj
. Simply open the solution file and run the project; no additional configuration should be necessary.
CMake can also be used to build the documentation and unit tests. An out-of-source build is recommended. In this example, we will do an out-of-source build in the build
directory:
Unit tests are built by default. Enable the BUILD_DOC
CMake flag to also build documentation (requires Doxygen).
https://d-bahr.github.io/CRCpp/
CRC++ is free to use and provided under a BSD license.
Catalog of CRCs: https://reveng.sourceforge.io/crc-catalogue/
5G-NR Specification 3GPP TS 38.212: https://www.etsi.org/deliver/etsi_ts/138200_138299/138212/15.03.00_60/ts_138212v150300p.pdf
USB 2.0 Specification: https://www.usb.org/document-library/usb-20-specification