mirror of
https://github.com/haproxy/haproxy.git
synced 2026-02-25 10:50:31 -05:00
70bcfb77a7
GCC4 is stupid (unbelievable news!). When some code uses __builtin_expect(x != 0, 1), it really performs the check of x != 0 then tests that the result is not zero! This is a double check when only one was expected. Some performance drops of 10% in the HTTP parser code have been observed due to this bug. GCC 3.4 is fine though. A solution consists in expecting that the tested value is 1. In this case, it emits the correct code, but it's still not optimal it seems. Finally the best solution is to ignore likely() and to pray for the compiler to emit correct code. However, we still have to fix unlikely() to remove the test there too, and to fix all code which passed pointers overthere to pass integers instead. |
||
|---|---|---|
| .. | ||
| appsession.h | ||
| base64.h | ||
| cfgparse.h | ||
| compat.h | ||
| config.h | ||
| debug.h | ||
| defaults.h | ||
| eb32tree.h | ||
| eb64tree.h | ||
| ebpttree.h | ||
| ebtree.h | ||
| epoll.h | ||
| errors.h | ||
| memory.h | ||
| mini-clist.h | ||
| rbtree.h | ||
| regex.h | ||
| sessionhash.h | ||
| standard.h | ||
| template.h | ||
| time.h | ||
| tools.h | ||
| uri_auth.h | ||
| version.h | ||