Date: Fri, 07 Oct 2005 20:17:43 +0200 From: Andreas Kohn <andreas.kohn@gmx.net> To: Brooks Davis <brooks@one-eyed-alien.net> Cc: freebsd-hackers@freebsd.org Subject: Re: struct timeval: why is tv_sec long? Message-ID: <1128709063.1022.9.camel@klamath.syndrom23.de> In-Reply-To: <20051007162846.GB12691@odin.ac.hmc.edu> References: <1128644542.1273.36.camel@klamath.syndrom23.de> <20051007162846.GB12691@odin.ac.hmc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-OiADRL+wJFCq+DldCtIt Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi, On Fri, 2005-10-07 at 09:28 -0700, Brooks Davis wrote: > On Fri, Oct 07, 2005 at 02:22:22AM +0200, Andreas Kohn wrote: > > Hi, > >=20 > > is there any special reason for timeval.tv_sec being long? >=20 > tv_sec is presumably long becuase that way 64-bit platforms end up with > timevals that don't suffer from the 2038 bug. time_t is also long (or > rather synonimous with it) on all but alpha platforms. Thanks for this explanation. As SUSv2 wants tv_sec to be time_t[1], would it be possible to change this to time_t on all but alpha? I guess alpha will not receive a switch to long anymore[2].=20 This would still require workarounds as you suggested below for alpha (nothing changes here), but would at least bring !alpha closer to standards compliance, which would be a good thing IMVHO. > > and this fails to compile on FreeBSD.=20 >=20 > You probably can just cast the tv.tv_sec to a time_t. Alternativly, you > could allocate a time_t and assing tv_sec to it since that will work on > alpha where the other won't. Yep, I did the latter, and it works. Thanks. Regards, Andreas [1] http://www.opengroup.org/onlinepubs/007908799/xsh/systime.h.html [2] I read the instructions for sparc64, it that looked ugly and difficult.=20 --=20 <TalisA> was macht man eigentlich auf einer linux-gamer lan ? hl server aufsetzen und freuen ? *duck* ^^ --=-OiADRL+wJFCq+DldCtIt Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQBDRrvHYucd7Ow1ygwRAjzQAJ40QsZ6hvdiUH7EwfOVR5DbgUJscACeNasm a1xfXIuUukYjSeCFrYq/g3c= =Cxa4 -----END PGP SIGNATURE----- --=-OiADRL+wJFCq+DldCtIt--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1128709063.1022.9.camel>