time_t on sparc64
kris at obsecurity.org
Wed Oct 15 00:51:16 PDT 2003
On Wed, Oct 15, 2003 at 12:44:37AM -0700, Marcel Moolenaar wrote:
> 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.
I'd much prefer we get it over with now before sparc64 gets widely
deployed. It's going to be much more painful once there's an
installed user base running production 5.x-STABLE systems.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-standards/attachments/20031015/19c1cd0e/attachment.bin
More information about the freebsd-standards