From owner-freebsd-arch Sat Oct 27 17:36:56 2001 Delivered-To: freebsd-arch@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 106C537B406 for ; Sat, 27 Oct 2001 17:36:54 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id f9S0arb89926; Sat, 27 Oct 2001 17:36:53 -0700 (PDT) (envelope-from dillon) Date: Sat, 27 Oct 2001 17:36:53 -0700 (PDT) From: Matthew Dillon Message-Id: <200110280036.f9S0arb89926@apollo.backplane.com> To: arch@freebsd.org Subject: Re: 64 bit times revisited.. 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 World will build with 64 bit time_t. There was one fatal error in /usr.sbin/md5/md5.c. I really expected there to be more problems but it looks like most of the programs are type-agnostic. 'dd' converts time to doubles, for example, before it does anything. I'm doing a more complete audit now. There will certainly be a number of programs which truncate to sizeof(long) or sizeof(void *) or sizeof(int). 'make' does all three :-) I expect there to be others, but nothing that we would have to fix immediately (though I will fix them as I come across them). So far it's been amazingly painless. I really don't think this is going to be as big a deal as some people think (or even as big a deal as I thought it would be, I'm already half way there!). The next step for me is to write the syscall roll functions and test a 64 bit time_t kernel with a 32 bit time_t userland. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message