[PATCH 08/27] bfd/ELF: mark internal MIPS functions hidden
Maciej W. Rozycki
macro@orcam.me.uk
Mon Nov 3 14:28:52 GMT 2025
More information about the Binutils mailing list
Mon Nov 3 14:28:52 GMT 2025
- Previous message (by thread): [FOSDEM 2026] Call for Participation: GCC (GNU Toolchain) Devroom
- Next message (by thread): [PATCH 08/27] bfd/ELF: mark internal MIPS functions hidden
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, 28 Oct 2025, Jan Beulich wrote: > >> This reduces the dynamic symbol table some and allows the compiler to be > >> more aggressive about inlining (as it sees fit, of course). > > > > Fine with me, thanks (for whoever cares to build BFD as a DSO). > > Many (most?) distros do, I think. (As personally I do, fwiw.) I wonder what the rationale is for a private library (or a set of two, as opcodes is the other one). There's hardly if any benefit from page sharing (executables themselves share them anyway where run concurrently and there are so few of them). There's no benefit from being able to upgrade just the libraries as there is no stable ABI and they're tied to the executables built against them. But there's the performance hit from PIC code overhead and the increased startup latency from dynamic loading. There's the mess to handle too, when you have multiple configurations of cross-binutils installed, each requiring its own copies of BFD/opcodes for its specific target(s). But of course you're free to do so. Maciej
- Previous message (by thread): [FOSDEM 2026] Call for Participation: GCC (GNU Toolchain) Devroom
- Next message (by thread): [PATCH 08/27] bfd/ELF: mark internal MIPS functions hidden
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Binutils mailing list