From owner-freebsd-arch@FreeBSD.ORG Tue Sep 16 21:26:18 2008 Return-Path: Delivered-To: arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0E0F01065674 for ; Tue, 16 Sep 2008 21:26:18 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id A92158FC15 for ; Tue, 16 Sep 2008 21:26:17 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.61.3]) by phk.freebsd.dk (Postfix) with ESMTP id 0C27C170E4; Tue, 16 Sep 2008 21:26:15 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.2/8.14.2) with ESMTP id m8GLQEKm075969; Tue, 16 Sep 2008 21:26:15 GMT (envelope-from phk@critter.freebsd.dk) To: Brooks Davis From: "Poul-Henning Kamp" In-Reply-To: Your message of "Tue, 16 Sep 2008 16:16:47 EST." <20080916211646.GA35778@lor.one-eyed-alien.net> Date: Tue, 16 Sep 2008 21:26:14 +0000 Message-ID: <75968.1221600374@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: arch@freebsd.org, John Hein Subject: Re: 64 bit time_t X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2008 21:26:18 -0000 In message <20080916211646.GA35778@lor.one-eyed-alien.net>, Brooks Davis writes : > >--PEIAKu/WMn1b1Hv9 >Content-Type: text/plain; charset=us-ascii >Content-Disposition: inline > >On Tue, Sep 16, 2008 at 02:17:16PM -0600, John Hein wrote: >> Other than recompiling for -current users (and not being an MFC-able >> change and possibly breaking a gazillion unfortunately written ports), >> are their any other issues with switching to 64 bit time_t for i386? >> I suppose compat libs are a bit dicey. > >Off hand: every syscall that takes a time_t or a structure containing >a time_t would have to be reimplemented and a compatability version[...] This is a pretty nasty piece of work because it also involves the timespec and timeval structures which appear in ioctls, socket options, socket messages and so on. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.