[cutting the cc list down to bug-gnulib]
Surely that's not enough; we'd need to replace realloc on current glibc
platforms, and not replace realloc on hypothetical future glibc
platforms that behave more compatibly with the rest of the world.
Also, is reallocarray similarly afflicted? (I have
On 2024-10-18 05:30, Douglas McIlroy wrote:
> Regardless of the behavior of malloc(0), one expects this theorem to
> hold:
>
> Given that p = malloc(n) is not NULL, that 0<=m<=n, and that
> malloc(m) could in some
> circumstance return a non-null pointer, then realloc(p,m) will
> re
Simon Josefsson wrote:
> Should config.rpath be fixed too?
Good point.
Probably not: config.rpath is derived from libtool's m4/libtool.m4, which
does not have this second sentence (yet).
Bruno
