[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMdZqKH+qSuG_wCqH0CV3MxEuxfjwFRHZJ48=RPGyKQM1zj1FQ@mail.gmail.com>
Date: Mon, 10 Jul 2023 23:27:08 -0700
From: Mark Harris <mark.hsj@...il.com>
To: Paul Eggert <eggert@...ucla.edu>, libc-coord@...ts.openwall.com
Subject: Re: [PATCH v4] off64_t: prefer off_t for splice, etc.
Paul Eggert <eggert@...ucla.edu> wrote:
> +.SH NOTES
> +.B _FILE_OFFSET_BITS
> +should be defined to be 64 in code that uses a pointer to
> +.BR readahead ,
> +if the code is intended to be portable
> +to traditional 32-bit x86 and ARM platforms where
> +.BR off_t 's
> +width defaults to 32 bits.
These notes apply to any 32-bit platform that may default to a 32-bit
off_t (including not only x86 and ARM, but also C-SKY, HP-PA, m68k,
MicroBlaze, MIPS, Nios II, PowerPC, s390, SPARC, and SuperH). Is
there a need to specify "x86 and ARM", or could these three words be
omitted from each of the notes?
- Mark
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
