Date: Wed, 15 Oct 2003 00:44:37 -0700 From: Marcel Moolenaar <marcel@xcllnt.net> To: Harti Brandt <brandt@fokus.fraunhofer.de> Cc: sparc64@freebsd.org Subject: Re: time_t on sparc64 Message-ID: <20031015074437.GA60338@dhcp01.pn.xcllnt.net> In-Reply-To: <20031015090422.M57857@beagle.fokus.fraunhofer.de> References: <20031013153219.H45269@beagle.fokus.fraunhofer.de> <20031014103446.U45269@beagle.fokus.fraunhofer.de> <20031015045429.Q41837@gamplex.bde.org> <20031014225053.GA59096@dhcp01.pn.xcllnt.net> <20031015090422.M57857@beagle.fokus.fraunhofer.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Oct 15, 2003 at 09:06:38AM +0200, Harti Brandt wrote: > MM> > MM>BTW: time_t on ia64 is already 64 bit. > > Hmm. In this case it should be rather easy to change sparc64's time_t to > 64bit? Yes. The MI code is already done and there's not much MD code that is expected to break. It's mostly the structures that change. This is especially painful on sparc64 because it's big-endian. I assume that sparc64 passes syscall arguments in registers, so the syscalls that take a time_t do not change except that there's no sign extension prior to use. You can preserve the ABI until 2038 by ignoring the upper 32-bits in that case. -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031015074437.GA60338>