On 2024-11-05 14:33, Bruno Haible wrote:
malloc (0, 0) → malloc (0)
Thanks, fixed in both Autoconf and Gnulib.
Paul Eggert wrote:
> +# _AC_FUNC_MALLOC_IF(IF-WORKS, IF-NOT, UNKNOWN-ASSUME)
> +#
> +# If 'malloc (0, 0)' returns nonnull, run IF-WORKS, otherwise, IF-NOT.
Typo in comment:
malloc (0, 0) → malloc (0)
Bruno
On 2024-10-31 17:30, Bruno Haible wrote:
There is no harm, right.
OK, thanks, I patched Autoconf and propagated it into Gnulib as per
attached.From c7f29c827df9284ec56233c515286c4d57361e4c Mon Sep 17 00:00:00 2001
From: Paul Eggert
Date: Thu, 31 Oct 2024 19:22:22 -0700
Subject: [PATCH] malloc
Paul Eggert wrote:
> > This change fixes it (but obviously needs NOT be backpropagated into
> > Autoconf).
>
> I'd rather keep them in sync, though. No harm in that, right?
There is no harm, right.
Bruno
On 2024-10-31 14:11, Bruno Haible wrote:
This change fixes it (but obviously needs NOT be backpropagated into
Autoconf).
I'd rather keep them in sync, though. No harm in that, right?
Paul Eggert wrote:
> Sync from bleeding-edge Autoconf. All uses changed.
When using
- current gnulib,
- Autoconf 2.72,
- a configure.ac file that invokes AC_FUNC_MALLOC,
I see the following change in the generated configure file:
| gnu* | *-musl* | midipix* | midnightbsd* \
Paul Eggert wrote:
> + * m4/malloc.m4 (_AC_FUNC_MALLOC_IF):
> + * m4/realloc.m4 (_AC_FUNC_REALLOC_IF):
> + Sync from bleeding-edge Autoconf. All uses changed.
Since the context of evaluation of the third argument of
_AC_FUNC_MALLOC_IF, _AC_FUNC_REALLOC_IF is unspecified (and
could thu
* m4/malloc.m4 (_AC_FUNC_MALLOC_IF):
* m4/realloc.m4 (_AC_FUNC_REALLOC_IF):
Sync from bleeding-edge Autoconf. All uses changed.
---
ChangeLog | 5 +
m4/eealloc.m4 | 8 +---
m4/malloc.m4 | 29 +++--
m4/realloc.m4 | 28 ++--
4 files cha
