Re: doc: Clarify list of platforms for year2038 support

On 11/04/23 18:58, Paul Eggert wrote: > On 4/11/23 06:45, Adhemerval Zanella Netto wrote: > >> It makes difference on all ABIs with has originally 32 bit time_t support: >> i686, microblaze, arm, m68k, sh, csky, nios2, and hppa, powerpc32, sparc32, >> s390, and mips o32. > > Thanks, I installe

Re: doc: Clarify list of platforms for year2038 support

On 4/11/23 06:45, Adhemerval Zanella Netto wrote: It makes difference on all ABIs with has originally 32 bit time_t support: i686, microblaze, arm, m68k, sh, csky, nios2, and hppa, powerpc32, sparc32, s390, and mips o32. Thanks, I installed the attached. It also mentions Android, which still

Re: doc: Clarify list of platforms for year2038 support

On 11/04/23 02:33, Paul Eggert wrote: > Oh, I forgot to send comments that partly explain my recent changes in this > area. Here they are, belatedly: > > > On 2023-04-10 05:56, Bruno Haible wrote: > >> +@item >> +Linux/riscv32, > > says this platform used 6

Re: doc: Clarify list of platforms for year2038 support

Oh, I forgot to send comments that partly explain my recent changes in this area. Here they are, belatedly: On 2023-04-10 05:56, Bruno Haible wrote: +@item +Linux/riscv32, says this platform used 64-bit time_t "from the get go". +Linux with musl libc on

doc: Clarify list of platforms for year2038 support

Would anyone have guessed that the outcomes is ERROR for mips n32 but OK for x86_64 x32 ?) So, let me include this list in the documentation. 2023-04-10 Bruno Haible doc: Clarify list of platforms for year2038 support. * doc/year2038.texi (Avoiding the year 2038 problem): Lis