[RFC v2] Add [v]aprintf(3)

[Alejandro Colomar]

Hi Adhemerval,

On 2026-03-17T17:16:06-0300, Adhemerval Zanella Netto wrote:
> The below range-diff should fix the issue and export the symbols.

Thanks!  I've applied it, and it builds.

> Any *hidden_def should be paired with *hidden_proto, otherwise you get
> these crypt messages.
> 
> Also, the hidden proto/def is only required iff you intend to use the
> symbol internall on glibc and also export it as a public symbol (so
> the internal usage is binding to the internal symbol like -Bsymbolic).
> Otherwise if you just want to export it there is no need of it.

I think it'd be nice to use it internally in the future (just like
everything, I guess).

> 
> There is also the question if we need to nldbl variants for some ABIs
> (I don't recall in details the issue).

I don't know what ldbl and nldbl are, so I can't tell.

> We will need proper documentation,

Yup.  We already have a manual page for them; I'll now add the glibc
documentation in the patch.  This should be the easy part.  :)

> some regressions tests,

I'll try to imitate the vasprintf(3) tests.  I found there's
"libio/tst-asprintf-null.c".

> and the
> fortification wrapper.

Okay; I'll try this too.

[...]
> diff --git a/stdio-common/Versions b/stdio-common/Versions
> index 8e1cbf8559..ab1713f978 100644
> --- a/stdio-common/Versions
> +++ b/stdio-common/Versions
> @@ -71,6 +71,9 @@ libc {
>      __isoc23_sscanf;
>      __isoc23_vsscanf;
>    }
> +  GLIBC_2.44 {
> +    aprintf; vaprintf;
> +  }

I've put vaprintf in libio/Versions.


Cheers,
Alex

-- 
<https://www.alejandro-colomar.es>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://sourceware.org/pipermail/libc-alpha/attachments/20260317/d233cc35/attachment-0001.sig>