4fe06d8c83
In quic_transport_params_store(), we call qc_early_transport_params_cpy() if edata_accepted is set, which copies one by one all tx_params into the locally allocated etps struct, and later after updates we call qc_early_transport_params_validate() to check if they changed. It turns out that when USE_TRACE is disabled, gcc 4 to 13 are confused and believe that one or several of the fields compared in the later function might be used uninitialized. A careful code inspection proves that this is not the case. Setting them to zero in the _cpy() function makes the warning disappear, it's really an issue related to variable propagation it seems, which can explain why it doesn't happen with traces (code is a bit more complex). Gcc-13 only emits a warning about a single field, and gcc-14 completely solved it. Playing with consts, __maybe_unused etc has no effect. One thing works however, it is to mark the _validate() function noinline. In this case it is implemented normally and the compiler doesn't put its nose into the propagation path and doesn't complain. Such comments are always scary because one may seriously wonder whether the compiler emits valid code when it says this... It should be backported to 3.4 which experiences the same warning with USE_TRACE=0. |
||
|---|---|---|
| .github | ||
| addons | ||
| admin | ||
| dev | ||
| doc | ||
| examples | ||
| include | ||
| reg-tests | ||
| scripts | ||
| src | ||
| tests | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .travis.yml | ||
| BRANCHES | ||
| BSDmakefile | ||
| CHANGELOG | ||
| CONTRIBUTING | ||
| INSTALL | ||
| LICENSE | ||
| MAINTAINERS | ||
| Makefile | ||
| README.md | ||
| SUBVERS | ||
| VERDATE | ||
| VERSION | ||
HAProxy
HAProxy is a free, very fast and reliable reverse-proxy offering high availability, load balancing, and proxying for TCP and HTTP-based applications.
Installation
The INSTALL file describes how to build HAProxy. A list of packages is also available on the wiki.
Getting help
The discourse and the mailing-list are available for questions or configuration assistance. You can also use the slack or IRC channel. Please don't use the issue tracker for these.
The issue tracker is only for bug reports or feature requests.
Documentation
The HAProxy documentation has been split into a number of different files for ease of use. It is available in text format as well as HTML. The wiki is also meant to replace the old architecture guide.
Please refer to the following files depending on what you're looking for:
- INSTALL for instructions on how to build and install HAProxy
- BRANCHES to understand the project's life cycle and what version to use
- LICENSE for the project's license
- CONTRIBUTING for the process to follow to submit contributions
The more detailed documentation is located into the doc/ directory:
- doc/intro.txt for a quick introduction on HAProxy
- doc/configuration.txt for the configuration's reference manual
- doc/lua.txt for the Lua's reference manual
- doc/SPOE.txt for how to use the SPOE engine
- doc/network-namespaces.txt for how to use network namespaces under Linux
- doc/management.txt for the management guide
- doc/regression-testing.txt for how to use the regression testing suite
- doc/peers.txt for the peers protocol reference
- doc/coding-style.txt for how to adopt HAProxy's coding style
- doc/internals for developer-specific documentation (not all up to date)
License
HAProxy is licensed under GPL 2 or any later version, the headers under LGPL 2.1. See the LICENSE file for a more detailed explanation.