Date: Tue, 16 Sep 2008 21:26:14 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Brooks Davis <brooks@freebsd.org> Cc: arch@freebsd.org, John Hein <jhein@timing.com> Subject: Re: 64 bit time_t Message-ID: <75968.1221600374@critter.freebsd.dk> In-Reply-To: Your message of "Tue, 16 Sep 2008 16:16:47 EST." <20080916211646.GA35778@lor.one-eyed-alien.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?75968.1221600374>