Date: Wed, 15 Oct 2003 01:56:59 -0700 From: John-Mark Gurney <gurney_j@efn.org> To: Marcel Moolenaar <marcel@xcllnt.net> Cc: sparc64@freebsd.org Subject: Re: time_t on sparc64 Message-ID: <20031015085659.GX533@funkthat.com> In-Reply-To: <20031015074437.GA60338@dhcp01.pn.xcllnt.net> 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> <20031015074437.GA60338@dhcp01.pn.xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Marcel Moolenaar wrote this message on Wed, Oct 15, 2003 at 00:44 -0700:
> 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.
There is if you load a signed 32bit value into the register... sparc
will automaticly sign extend the register when loading a 32bit value..
This was done to be backwards compatible with sparcv8.
So the question is, does the values get loaded into different registers?
or are they packed into a single register?
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031015085659.GX533>