Re: Are you doing this too for GNU/Hurd?
Svante Signell, le jeu. 22 févr. 2024 18:13:50 +0100, a ecrit: > On Thu, 2024-02-22 at 17:43 +0100, Samuel Thibault wrote: > > Svante Signell, le jeu. 22 févr. 2024 17:36:15 +0100, a ecrit: > > > Changes: > > > ... > > > gcc-13 (13.2.0-14) experimental; urgency=medium > > > * Pass -D_TIME_BITS=64 together with -D_FILE_OFFSET_BITS=64 by > > > default > > > on the 32bit architectures armel, armhf, hppa, m68k, mips, > > > mipsel, > > > powerpc (-m32 only) and sh4. > > > ... > > > > No, just like it's not planned for i386. > > And why is it not planned for i386? I won't rehash the whole complex rationale that was discussed. What I essentially remember from it is that since this changes the ABI, this breaks compatibility with pre-built binaries downloadable from the Internet, so better leave them with the y2038 problem until then rather than breaking them now. Concerning the Hurd were we don't really have that problem, it's still a lot of work while on the long run we should just migrate to amd64. Samuel
Re: Are you doing this too for GNU/Hurd?
On 22 Feb 2024, at 17:13, Svante Signell wrote: > On Thu, 2024-02-22 at 17:43 +0100, Samuel Thibault wrote: >> Svante Signell, le jeu. 22 févr. 2024 17:36:15 +0100, a ecrit: >>> Changes: >>> ... >>> gcc-13 (13.2.0-14) experimental; urgency=medium >>> * Pass -D_TIME_BITS=64 together with -D_FILE_OFFSET_BITS=64 by >>> default >>> on the 32bit architectures armel, armhf, hppa, m68k, mips, >>> mipsel, >>> powerpc (-m32 only) and sh4. >>> ... >> >> No, just like it's not planned for i386. > > And why is it not planned for i386? See https://wiki.debian.org/ReleaseGoals/64bit-time. Jess
Re: Are you doing this too for GNU/Hurd?
On Thu, 2024-02-22 at 17:43 +0100, Samuel Thibault wrote: > Svante Signell, le jeu. 22 févr. 2024 17:36:15 +0100, a ecrit: > > Changes: > > ... > > gcc-13 (13.2.0-14) experimental; urgency=medium > > * Pass -D_TIME_BITS=64 together with -D_FILE_OFFSET_BITS=64 by > > default > > on the 32bit architectures armel, armhf, hppa, m68k, mips, > > mipsel, > > powerpc (-m32 only) and sh4. > > ... > > No, just like it's not planned for i386. And why is it not planned for i386?
Re: Are you doing this too for GNU/Hurd?
Svante Signell, le jeu. 22 févr. 2024 17:36:15 +0100, a ecrit: > Changes: > ... > gcc-13 (13.2.0-14) experimental; urgency=medium > * Pass -D_TIME_BITS=64 together with -D_FILE_OFFSET_BITS=64 by default > on the 32bit architectures armel, armhf, hppa, m68k, mips, mipsel, > powerpc (-m32 only) and sh4. > ... No, just like it's not planned for i386. Samuel
Are you doing this too for GNU/Hurd?
>From the changelog: Changes: ... gcc-13 (13.2.0-14) experimental; urgency=medium * Pass -D_TIME_BITS=64 together with -D_FILE_OFFSET_BITS=64 by default on the 32bit architectures armel, armhf, hppa, m68k, mips, mipsel, powerpc (-m32 only) and sh4. ...
