...
Cyclic Redundancy Check (CRC) is a standardized way to implement a degree of data validation and is used in various over the wire protocols, data checksums, etc. Naive implementations are a bitwise loop over an input message and highly inefficient. Detection of a CRC loop and transformation into either a table lookup or a combination of clmul + shift operations can speed up such code by 2X or more10X. This would include the CRC loop in the Coremark benchmark – detecting and optimizing that idiom results in about a 10% 10-20% improvement in Coremark scores depending on the micro-architecture.
The detection of a CRC loop is a complex optimization with elements of vectorization, feedback loops, pattern matching, etc. It is further complicated by function inlining. At this time we have patches for upstream GCC that can detect and generate code (either table lookup or clmul) for a variety of CRC implementations. An aggressive schedule would be integration in time for gcc-14, but more likely it will fall into gcc-15.
...
Ventana: Jeff Law – oversight, patch review
External:
Significant design work and theoretical background provided by Philipp Tomsich and Henry Brausen of VRULL
...
| Page Properties | ||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Updates
- Mariam has posted the CRC optimization work for upstream review. This includes methods to generate CRC using clmul, table lookups for RISC-V. For testing purposes it also supports AArch64 and x86_64's clmul variants as well as the x86_64 crc instruction if the proper polynomial is used.
- Jeff Law has started review work. Expecting to get input from Intel and ARM/Linaro engineers as the implementation includes support for those architectures.
- Simple tests using this code to detect a CRC loop that is compatible with the x86 crc32 instruction and generating the crc32 instruction for such loops show using the crc32 instruction is at least 5X faster than a loop.
- Currently investigating generating aarch64 clmul as there is a bit time to do this as a proof of concept before focusing on the upstreaming effort.
- It had been speculated that this work could generate a "crc" instruction on suitable ISAs if a loop with the right field polynomial were encountered. This has been implemented as a proof of concept on x86
- It has also been speculated that this work could be used to detect clmul idioms outside of a CRC loop. This appears to work by relaxing various aspects of the CRC loop verifier. It is not an area of focus though.
- Minor bugs have been fixed in the implementation as it is prepared for upstreaming. Goal is still integration for gcc-15 in the late spring.
- Implementation done for x86_64 using its clmul. Primary purpose was to show that using clmul, while requiring target specific development, is not a major effort. This is expected to help with the upstreaming effort.
- Code drop from 1/26 integrated into the upstream GCC tester.
- Expectation is to submit code for upstream review in Feb with a goal of integrating for gcc-15 in the late spring.
- Major cleanups/fixes have been made in the gimple→RTL code generation phase. At this point CRC detection and code generation using table lookups is expected to work on any architecture GCC supports. Additionally generation of clmul instructions is supported on RISC-V when the appropriate extension is enabled.
- At this point the development cycle is considered complete and we will be working through the usptreaming process with a target of inclusion in gcc-15 (spring 2025)
- Significant cleanup of backend support. Should (in theory) be target independent at this point. We'll do some testing on other targets to verify this shortly.
- Cleanup of the main recognizer and LFSR validation step in progress
- Evaluating the ability of Ranger to eliminate the need to introduce another symbolic engine.
- As noted before, not a great initial response to carving out the backend work and trying to upstream that for gcc-14
- Regardless, we're working through various review comments to make it more palatable for upstream gcc
- Generalize table based CRC generation so that it works on multiple targets
- Fix implementation details that would cause failures when running gcc on different host platforms targeting rv64
- Various coding convention, documentation and formatting issues necessary for upstreamingFocu
- Not a great initial response to builtin_crc to carve out initial backend work
- Still evaluating if there's a path forward without having to submit full end-to-end optimization
...