From owner-freebsd-arch@freebsd.org Fri Jun 24 11:10:07 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 1FDC8B738C3 for ; Fri, 24 Jun 2016 11:10:07 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id DDA532D9C for ; Fri, 24 Jun 2016 11:10:06 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.60.3]) by phk.freebsd.dk (Postfix) with ESMTP id 945AA273CD; Fri, 24 Jun 2016 11:10:05 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTP id u5OBA54M004659; Fri, 24 Jun 2016 11:10:05 GMT (envelope-from phk@phk.freebsd.dk) cc: Bruce Evans , freebsd-arch@freebsd.org Subject: Re: PowerPC 64-bit time_t In-reply-to: <4641.1466766430@critter.freebsd.dk> From: "Poul-Henning Kamp" References: <3FB65E20-0376-4041-86DE-F8CAB7F37314@freebsd.org> <20160609193128.GB34204@spindle.one-eyed-alien.net> <575A48D3.3090008@wemm.org> <20160624194454.D1013@besplex.bde.org> <4641.1466766430@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4657.1466766605.1@critter.freebsd.dk> Date: Fri, 24 Jun 2016 11:10:05 +0000 Message-ID: <4658.1466766605@critter.freebsd.dk> 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: Fri, 24 Jun 2016 11:10:07 -0000 -------- In message <4641.1466766430@critter.freebsd.dk>, "Poul-Henning Kamp" writes: >-------- >In message <20160624194454.D1013@besplex.bde.org>, Bruce Evans writes: > >>The only practical option for i386 is to change to unsigned time_t before >>2038 and hope that i386 goes away before that runs out in 2106. Changing >>to uint32_t time_t mainly requires doing something with times before the >>Epoch. These are unsupported in POSIX, but are supposed to work back to >>1902 with int32_t in FreeBSD, except 1 second before the Epoch is the >>same as the error code (time_t)(-1) so it doesn't work right. > >I'd recommend it, dates one timezones worth before epoch are far too >common in contemporary traffic (particular HTTP). It's too warm here: read: I'd recommend *against* it. >Why don't we make a i387[1] port where time_t is 64 bit and where we jettison >the museum-ready IBM PC baggage ? > > >[1] Of course a joke reference to floating point HW being mandatory. > >-- >Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 >phk@FreeBSD.ORG | TCP/IP since RFC 956 >FreeBSD committer | BSD since 4.3-tahoe >Never attribute to malice what can adequately be explained by incompetence. >_______________________________________________ >freebsd-arch@freebsd.org mailing list >https://lists.freebsd.org/mailman/listinfo/freebsd-arch >To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.