Date: Thu, 9 Jun 2016 16:38:34 -0400 From: Justin Hibbits <jhibbits@freebsd.org> To: Garance A Drosehn <drosih@rpi.edu> Cc: freebsd-arch@freebsd.org Subject: Re: PowerPC 64-bit time_t Message-ID: <51CA1453-0393-4D72-BAC6-053318B001E0@freebsd.org> In-Reply-To: <E252D041-6E31-40E6-8265-B7F9B8C8F191@rpi.edu> References: <3FB65E20-0376-4041-86DE-F8CAB7F37314@freebsd.org> <E252D041-6E31-40E6-8265-B7F9B8C8F191@rpi.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 9, 2016, at 4:22 PM, Garance A Drosehn wrote: > On 9 Jun 2016, at 13:41, Justin Hibbits wrote: > >> At the devsummit earlier today I mentioned for FreeBSD 12 wanting >> 64-bit time_t across the board. It was pointed out that the only >> ones with 32-bit time_t are i386 and powerpc (32-bit). I've made >> the changes necessary for at least kernel (world is still building >> right now), but it's obviously an ABI and KBI incompatible change. >> Addressing KBI is a nonissue, as that's expected to break at major >> releases. ABI is another issue. I'm unsure how to properly >> address ABI breakage -- bumping libc's .so version, or reversion >> all symbols that use something with time_t, or something else. If >> I can address it before the code freeze, it could be done for >> FreeBSD 11, which leaves about 6 hours from now. >> >> Any thoughts? > > I don't know if it would help to look at the changes done back when > sparc64 went to a 64-bit time_t. I did a lot of that work, but I'll > have to admit I remember almost nothing about the changes. > > -- > Garance Alistair Drosehn = drosih@rpi.edu > Senior Systems Programmer or gad@FreeBSD.org > Rensselaer Polytechnic Institute; Troy, NY; USA Thanks. The UPDATING.64BIT file you created for the upgrade path for sparc64 is an excellent source for the headaches involved with source based upgrades from 32-bit time_t to 64-bit. - Justin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51CA1453-0393-4D72-BAC6-053318B001E0>