Date: Mon, 22 Dec 2003 14:16:30 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: Peter Jeremy <peterjeremy@optushome.com.au>, Craig Boston <craig@xfoil.gank.org> Cc: current@freebsd.org Subject: Re: An experiment: 64-bit time_t on IA-32 (5.2-RC) Message-ID: <p0602040fbc0cf0dddf9e@[128.113.24.47]> 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
At 7:01 PM +1100 12/22/03, Peter Jeremy wrote: >On Sun, Dec 21, 2003, Craig Boston wrote: > > The initial compile went off without a hitch. This is no > > doubt due to hard work by the people working on the ia64, > > amd64, etc. ports where time_t is 64-bits by default. A > > side note, I noticed that the alpha and sparc64 ports > > seem to be using 32-bit time_t, which surprised me. > >Alpha has a 32-bit time_t for compatability with Tru64. There >are occasional discussions on -alpha regarding the pros and >cons of moving to 64-bits. I suspect SPARC is 32 bit for >Solaris compatability. 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. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p0602040fbc0cf0dddf9e>