Date: Thu, 9 Jun 2016 13:00:09 -0700 From: Nathan Whitehorn <nwhitehorn@freebsd.org> To: freebsd-arch@freebsd.org Subject: Re: PowerPC 64-bit time_t Message-ID: <ceaec140-6a03-ff9b-7fe8-50136ef7e77e@freebsd.org> In-Reply-To: <20160609193128.GB34204@spindle.one-eyed-alien.net> References: <3FB65E20-0376-4041-86DE-F8CAB7F37314@freebsd.org> <20160609193128.GB34204@spindle.one-eyed-alien.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 06/09/16 12:31, Brooks Davis wrote: > On Thu, Jun 09, 2016 at 01:41:52PM -0400, 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. > For i386, the only practical option is going to be a new TARGET_ARCH and > likely ELF machine type. > > For powerpc, I'd be tempted to just break the ABI and leave a way to switch > it back for people who build products where the ABI change is an issue. > > -- Brooks I would agree with this. -Nathan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ceaec140-6a03-ff9b-7fe8-50136ef7e77e>