From owner-freebsd-arch Sat Oct 27 21: 4: 1 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 3CF5337B401; Sat, 27 Oct 2001 21:03:58 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id f9S43vm88827; Sat, 27 Oct 2001 21:03:57 -0700 (PDT) (envelope-from dillon) Date: Sat, 27 Oct 2001 21:03:57 -0700 (PDT) From: Matthew Dillon Message-Id: <200110280403.f9S43vm88827@apollo.backplane.com> To: Mike Smith Cc: arch@FreeBSD.ORG Subject: Re: 64 bit times revisited.. References: <200110280349.f9S3n6v22087@mass.dis.org> 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 : :> 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. : :Please write a library routine that detects and compensates for: : : : int t; : : time(&t); : :Until you can do this, sorry, no. Sorry, your statement makes no sense. Besides, if the programmer includes time.h the above will generate compiler warnings, so that's actually the easiest case to catch. I'll tell you what, why don't YOU write a library routine that detects this: /* no includes */ int x; lseek(fd, x, 0); Oops! That doesn't work either! Are you going to change our off_t from 64 back to 32 bits? No? Well, then I'm afraid you are going to have to just live with it. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message