From owner-freebsd-arch Sat Oct 27 13:14:49 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 1CC5C37B403; Sat, 27 Oct 2001 13:14:47 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id f9RKEkj56354; Sat, 27 Oct 2001 13:14:46 -0700 (PDT) (envelope-from dillon) Date: Sat, 27 Oct 2001 13:14:46 -0700 (PDT) From: Matthew Dillon Message-Id: <200110272014.f9RKEkj56354@apollo.backplane.com> To: Peter Wemm Cc: Mike Smith , arch@FreeBSD.ORG Subject: Re: time_t not to change size on x86 References: <20011027201203.294B839F0@overcee.netplex.com.au> 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 - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au :> :> I think the absolute worst that can happen is that moving time_t to :> 64 bits will have the same sort of impact on ports that moving off_t to :> 64 bits had. I don't recall the off_t change as causing any significant :> pain. FreeBSD had it from the get-go, but most of our ports were :> compiled on systems with 32 bit off_t's. : :Glad you mentioned the off_t problem.. We're *still* finding off_t bugs :in *OUR OWN CODE*!! How long has off_t been long long? Nearly 8 years now :and we're *still* finding them! : :Cheers, :-Peter And I'm sure there are still K&R problems too. The point is that off_t being 64 bits has not posed a serious problem in at least 5 years, probably longer. It's completely off the radar screen. Are you seriously proposing that we change off_t back to 32 bits because of the minor little off-the-radar-almost-don't-matter bugs that come up every now and again? No? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message