From owner-freebsd-arch@freebsd.org Thu Jun 9 19:31:36 2016 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 755D1B7032D for ; Thu, 9 Jun 2016 19:31:36 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: from spindle.one-eyed-alien.net (spindle.one-eyed-alien.net [199.48.129.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 540C91FC6; Thu, 9 Jun 2016 19:31:36 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id F3C295A9F27; Thu, 9 Jun 2016 19:31:28 +0000 (UTC) Date: Thu, 9 Jun 2016 19:31:28 +0000 From: Brooks Davis To: Justin Hibbits Cc: freebsd-arch@freebsd.org Subject: Re: PowerPC 64-bit time_t Message-ID: <20160609193128.GB34204@spindle.one-eyed-alien.net> References: <3FB65E20-0376-4041-86DE-F8CAB7F37314@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2fHTh5uZTiUOsy+g" Content-Disposition: inline In-Reply-To: <3FB65E20-0376-4041-86DE-F8CAB7F37314@freebsd.org> User-Agent: Mutt/1.6.1 (2016-04-27) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2016 19:31:36 -0000 --2fHTh5uZTiUOsy+g Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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-=20 > bit time_t across the board. It was pointed out that the only ones =20 > with 32-bit time_t are i386 and powerpc (32-bit). I've made the =20 > changes necessary for at least kernel (world is still building right =20 > now), but it's obviously an ABI and KBI incompatible change. =20 > Addressing KBI is a nonissue, as that's expected to break at major =20 > releases. ABI is another issue. I'm unsure how to properly address =20 > ABI breakage -- bumping libc's .so version, or reversion all symbols =20 > that use something with time_t, or something else. If I can address =20 > it before the code freeze, it could be done for FreeBSD 11, which =20 > 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 --2fHTh5uZTiUOsy+g Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJXWcQQAAoJEKzQXbSebgfAlgwH/i/dMVG5k8zIiA4H1Nlcm+nz /zUIh9W0FYSIyP9iZjO3m0khnvqPZhf0H6tossmItgkQq9FyVGQWBiswzv3Xxqp5 sRvE863z8smCrMG7E39WazpwPLmaRVUu3wgFLir4aaI14bsYIbNsjRPEMdDJj3x8 J+6zgt2fEFiFpdmTQayQdV2PI5gL9VhFEzfnZu3vDbqNvQ4mSx5U0spedGqG+NoW GfnPQS4ZolNQgBzMpzJtXSlboKGn8OSzEGoFIyOWi6q5Gr4y1DeY38qp3i6SWwf0 zM+3lQgBXeeynGYUuOcWaEjC8sV/r6ave57r7nidzT1jwzHUS+BHbIFgWBVGwFQ= =10uM -----END PGP SIGNATURE----- --2fHTh5uZTiUOsy+g--