Date: Mon, 23 Feb 2004 13:42:34 -0500 From: John Baldwin <jhb@FreeBSD.org> To: sparc64@FreeBSD.org Cc: Garance A Drosihn <drosih@rpi.edu> Subject: Re: Problem with DHCLIENT vs 64-bit time_t Message-ID: <200402231342.34470.jhb@FreeBSD.org> In-Reply-To: <xzpllmuep88.fsf@dwp.des.no> References: <p06020407bc533f0ae9d2@[128.113.24.47]> <20040222191618.GB53610@dhcp01.pn.xcllnt.net> <xzpllmuep88.fsf@dwp.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday 22 February 2004 05:14 pm, Dag-Erling Sm=F8rgrav wrote: > Marcel Moolenaar <marcel@xcllnt.net> writes: > > This code is then obviously also broken on amd64 and ia64 [...] > > yep, if they have 64-bit time_t. They are little endian though, so treating a time_t * as an int32_t* direct= ly=20 still works ok (for some value of works). That is why only sparc64 has a=20 catastrophic failure. =2D-=20 John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =3D http://www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200402231342.34470.jhb>