From owner-freebsd-arch@FreeBSD.ORG Fri Nov 14 23:12:05 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B0A3D16A4D0; Fri, 14 Nov 2003 23:12:05 -0800 (PST) Received: from smtp4.server.rpi.edu (smtp4.server.rpi.edu [128.113.2.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id D662D43F3F; Fri, 14 Nov 2003 23:12:04 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp4.server.rpi.edu (8.12.10/8.12.9) with ESMTP id hAF7C4tp027558; Sat, 15 Nov 2003 02:12:04 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <3FB5C942.1010907@freebsd.org> References: <3FB5C942.1010907@freebsd.org> Date: Sat, 15 Nov 2003 02:12:02 -0500 To: Scott Long From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: CanIt (www . canit . ca) cc: arch@freebsd.org Subject: Re: 64-bit time_t on sparc64, epilogue(?) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Nov 2003 07:12:05 -0000 At 11:35 PM -0700 11/14/03, Scott Long wrote: >Garance A Drosihn wrote: >>Recently on the freebsd-sparc64 list, it was mentioned >>that it would be nice to upgrade time_t on that port to >>be 64-bit. [...mumble mumble...] >>So, I thought I'd explicitly say that I don't think we >>should make the change this late in the game.. > >Switching to 64-bit time_t this late in the 5.2 cycle will >likely cause more excitement than we can handle. ... >...Why don't we put this on the TODO list for 5.3, and >plan to do it in early January, assuming that Jake and >Thomas are ok with it. Personally I am inclined to think that we have to stop making ABI/API changes to 5.x or we will never ever get to "5.x-stable". It would be nice if 5.2 were the last set of API/ABI changes, so that people who install it can at least have a painless upgrade to 5.3-release (which will hopefully be 5.x-stable). However, I really would like to see the 64-bit time_t happen, and I'm certainly willing to help out (as time permits) if we were to make this change on sparc64 in early January. I'll even start testing such changes on my own sparc64 system during the code-freeze for 5.2. [however, it takes about 11 hours for build/installworld on my system, so there's a limit to how much I can test!] Certainly it's more important to get make-release and kse-for-sparc64 working for 5.2-release than it is to make this time_t change. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu