On Sun, Jun 04, 2023 at 01:38:39PM +0200, Arnd Bergmann wrote: > > Over time we managed > > to make simple code compile with both glibc and nolibc, but when it > > comes at the cost of adding size and burden for the developers, such > > as forcing them to add libgcc, I prefer that we slightly limit the > > domain of application instead. > > Good point. This also reminds me that the compilers I build for > https://mirrors.edge.kernel.org/pub/tools/crosstool/ don't always > have every version of libgcc that may be needed, for instance > the mips compilers only provide a big-endian libgcc and the > arm compilers only provide a little-endian one, even though > the compilers can build code both ways with the right flags. That reminds me something indeed, I know that MIPS is a great platform for testing portability due to libgcc and/or atomics not always being complete depending how it's built. At work when I double-check that haproxy still builds and starts on my EdgeRouter-X, then it will build everywhere ;-) Willy
