atom feed17 messages in org.freebsd.freebsd-standardstime_t on sparc64
FromSent OnAttachments
Harti BrandtOct 13, 2003 6:42 am 
Bruce EvansOct 13, 2003 11:20 am 
Harti BrandtOct 14, 2003 1:40 am 
Garance A DrosihnOct 14, 2003 10:52 am 
Bruce EvansOct 14, 2003 12:30 pm 
Marcel MoolenaarOct 14, 2003 3:51 pm 
Marcel MoolenaarOct 15, 2003 12:46 am 
Kris KennawayOct 15, 2003 12:53 am 
John-Mark GurneyOct 15, 2003 1:57 am 
Harti BrandtOct 15, 2003 2:02 am 
Garance A DrosihnOct 15, 2003 11:57 am 
Marcel MoolenaarOct 15, 2003 12:10 pm 
Garance A DrosihnOct 15, 2003 1:14 pm 
Harti BrandtOct 15, 2003 11:26 pm 
Harti BrandtOct 16, 2003 3:48 am 
Garance A DrosihnOct 17, 2003 12:28 pm 
Harti BrandtOct 20, 2003 1:01 am 
Subject:time_t on sparc64
From:Marcel Moolenaar (mar@xcllnt.net)
Date:Oct 15, 2003 12:46:35 am
List:org.freebsd.freebsd-standards

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.