Date: Sun, 4 Jan 2004 20:59:37 -0800 From: "David O'Brien" <obrien@freebsd.org> To: Garance A Drosihn <drosih@rpi.edu>, Harti Brandt <brandt@fokus.fraunhofer.de> Cc: freebsd-sparc64@freebsd.org Subject: Re: An experiment: 64-bit time_t on IA-32 (5.2-RC) Message-ID: <20040105045937.GC25184@dragon.nuxi.com> In-Reply-To: <p0602040fbc0cf0dddf9e@[128.113.24.47]> References: <200312212239.38557.craig@xfoil.gank.org> <20031222080115.GA645@server.vk2pj.dyndns.org> <p0602040fbc0cf0dddf9e@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Dec 22, 2003 at 02:16:30PM -0500, Garance A Drosihn wrote: > Note that there it is likely we will switch sparc64 to a > 64-bit time_t before 5.3 is released. We talked about making > that change sometime in January, once we would be sure that > 5.2-release was settled. On Tue, Dec 23, 2003 at 10:09:53AM +0100, Harti Brandt wrote: > time_t is a long on Solaris and hence 64bit (when compiling in 64-bit > mode). Compatibility (with Solaris and Posix) requires time_t to be > 64-bit > and tv_sec to be a time_t. I hope we will get this right until > 5.3 goes out. I'm running with a 64-bit time_t for two months now > without problems. Before the tree starts to get disruptive and unstable on the push to 5.3; maybe this is a good time to make the switch to 64-bit time_t for sparc64. -- David
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040105045937.GC25184>