diff options
| author | Sergei Zimmerman <sergei@zimmerman.foo> | 2025-09-29 01:46:40 +0300 |
|---|---|---|
| committer | Philip Taron <philip.taron@gmail.com> | 2025-10-07 14:37:16 -0700 |
| commit | c1e3ab069ccb4d4ca645c3fff0dc95f4ec26c54e (patch) | |
| tree | f4e13fc11bca1f6a353bb31a3ea2fffadae01d30 /pkgs/development/python-modules/rangehttpserver | |
| parent | 46a5936eecefd6eb8bdd67f9dace188f3d84993c (diff) | |
packaging: Build without symbolic interposition on GCC
This turns out to be a big problem for performance of Bison
generated code, that for whatever reason cannot be made internal
to the shared library. This causes GCC to make a bunch of function
calls go through PLT. Ideally these hot functions (like move/copy ctor) could become
inline in upstream Bison. That will make sure that GCC can do interprocedular
optimizations without -fno-semantic-interposition [^]. Considering that
LLVM already does inlining and whatnot is a good motivation for this change.
I don't know of any case where Nix relies on LD_PRELOAD tricks for the shared
libraries in production use-cases.
[^]: https://maskray.me/blog/2021-05-09-fno-semantic-interposition
Diffstat (limited to 'pkgs/development/python-modules/rangehttpserver')
0 files changed, 0 insertions, 0 deletions