From owner-freebsd-arch Thu Oct 25 21:46: 8 2001 Delivered-To: freebsd-arch@freebsd.org Received: from coffee.q9media.com (coffee.q9media.com [216.94.229.19]) by hub.freebsd.org (Postfix) with ESMTP id 6B83C37B403 for ; Thu, 25 Oct 2001 21:46:05 -0700 (PDT) Received: (from mike@localhost) by coffee.q9media.com (8.11.6/8.11.6) id f9Q4nj298811; Fri, 26 Oct 2001 00:49:45 -0400 (EDT) (envelope-from mike) Date: Fri, 26 Oct 2001 00:49:45 -0400 From: Mike Barcroft To: Peter Wemm Cc: arch@FreeBSD.ORG Subject: Re: 64 bit times revisited.. Message-ID: <20011026004945.I93553@coffee.q9media.com> References: <20011025233602.587C63808@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011025233602.587C63808@overcee.netplex.com.au>; from peter@wemm.org on Thu, Oct 25, 2001 at 04:36:02PM -0700 Organization: The FreeBSD Project Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Peter Wemm writes: > 4) Pro: > All wire and on-disk formats mentioning time_t will be compatable > across the entire freebsd range. > The Pentium21 (to be released in year 2021) will be Y2038 safe. :-) > Con: > Break i386 *.o compatability. We would be subjecting ourselves to > the same sort of pain that the rest of the unix world went through > (and is still going through with the 64 bit filesize transition). > Doesn't solve things like "int32_t start_time;" in exposed disk and > on-the-wire structures. > Printf format hell (%qd on i386, %ld on the 64 bit platforms) where > it causes real screwups if there is a mistake. I vote for 4. The issue with printf(9) could be solved by using the new C99 type intmax_t (which defines the largest possible integer type available) and printf() counterpart %j. Ofcourse this might be a problem if we port to a 128 bit processor. Best regards, Mike Barcroft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message