Date: Tue, 23 Dec 2003 10:09:53 +0100 (CET) From: Harti Brandt <brandt@fokus.fraunhofer.de> To: Peter Jeremy <peterjeremy@optushome.com.au> Cc: current@freebsd.org Subject: Re: An experiment: 64-bit time_t on IA-32 (5.2-RC) Message-ID: <20031223100005.X53278@beagle.fokus.fraunhofer.de> In-Reply-To: <20031222080115.GA645@server.vk2pj.dyndns.org> References: <200312212239.38557.craig@xfoil.gank.org> <20031222080115.GA645@server.vk2pj.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 22 Dec 2003, Peter Jeremy wrote: PJ>On Sun, Dec 21, 2003 at 10:39:38PM -0600, Craig Boston wrote: PJ>>The initial compile went off without a hitch. This is no doubt due to hard PJ>>work by the people working on the ia64, amd64, etc. ports where time_t is PJ>>64-bits by default. A side note, I noticed that the alpha and sparc64 ports PJ>>seem to be using 32-bit time_t, which surprised me. PJ> PJ>Alpha has a 32-bit time_t for compatability with Tru64. There are PJ>occasional discussions on -alpha regarding the pros and cons of moving PJ>to 64-bits. I suspect SPARC is 32 bit for Solaris compatability. 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. harti -- harti brandt, http://www.fokus.fraunhofer.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.fraunhofer.de, harti@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031223100005.X53278>