| commit | af3627218c7e379d3d9c681ec395d3634b5533eb | [log] [tgz] |
|---|---|---|
| author | ricea <ricea@google.com> | Wed Sep 24 10:03:58 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Sep 24 10:05:00 2025 -0700 |
| tree | b76c1109a5139788675e963e146cef1b632b9f27 | |
| parent | 5a4893ec463e29f40658b53b1326ef9b76748981 [diff] |
Stop link clashes in QUICHE fuzzers The copybara-generated sources-list.gni file makes it simplest to link all QUICHE fuzzers into a single binary. Unfortunately, many QUICHE fuzzers contain a function named DoesNotCrash() which results in linking errors when multiple such functions are linked into a single binary. Place all the fuzzer code inside anonymous namespaces to avoid linking errors when they are linked together. In some cases, DoesNotCrash() was defined in the global namespace. Place it inside the `quic` namespace and remove unnecessary `quic::` namespace qualifications. No functional changes. PiperOrigin-RevId: 810928409
QUICHE stands for QUIC, Http, Etc. It is Google‘s production-ready implementation of QUIC, HTTP/2, HTTP/3, and related protocols and tools. It powers Google’s servers, Chromium, Envoy, and other projects. It is actively developed and maintained.
There are two public QUICHE repositories. Either one may be used by embedders, as they are automatically kept in sync:
To embed QUICHE in your project, platform APIs need to be implemented and build files need to be created. Note that it is on the QUICHE team's roadmap to include default implementation for all platform APIs and to open-source build files. In the meanwhile, take a look at open source embedders like Chromium and Envoy to get started:
To contribute to QUICHE, follow instructions at CONTRIBUTING.md.
QUICHE is only supported on little-endian platforms.