Hi Jim, Paul,
Paul Eggert writes:
> On 2024-08-13 09:20, Jim Meyering wrote:
>> While somewhat related, I don't see how an async-safe strcpy would let
>> us remove that function.
>
> Agreed. You can't even use strcpy on 'char volatile *'; C prohibits
> that. Async safety is about something else
On 2024-08-13 09:20, Jim Meyering wrote:
While somewhat related, I don't see how an async-safe strcpy would let
us remove that function.
Agreed. You can't even use strcpy on 'char volatile *'; C prohibits
that. Async safety is about something else (admittedly brain-hurting :-).
On Sun, Aug 4, 2024 at 5:10 PM Collin Funk wrote:
> Also, now that POSIX-1.2024 requires strcpy to be async-signal-safe can
> 'volatile_strcpy' be removed? Or is there something more to
> that. Signals hurt my brain a bit, sorry...
While somewhat related, I don't see how an async-safe strcpy woul
Thanks! Applied
Since gzip uses 'printf-posix' can't offsets be printed using that
instead of fprint_off? Patch attached + 1 more removing #ifndef CHAR_BIT
cruft.
Also, now that POSIX-1.2024 requires strcpy to be async-signal-safe can
'volatile_strcpy' be removed? Or is there something more to
that. Signals hurt
