Date: Fri, 29 Apr 2011 13:24:12 -0600 From: Warner Losh <imp@bsdimp.com> To: "Jayachandran C." <c.jayachandran@gmail.com> Cc: Juli Mallett <jmallett@FreeBSD.org>, freebsd-mips@FreeBSD.org Subject: Re: 64 bit time_t in 32 bit ABI? Message-ID: <DD2906D8-811B-4CFB-B899-2AC88FF26720@bsdimp.com> In-Reply-To: <BANLkTimdbgabRCBbdjR1L45DtkETDT1UNw@mail.gmail.com> References: <BANLkTimdbgabRCBbdjR1L45DtkETDT1UNw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I thought we made all new architectures adopt a 32-bit time_t and that's = why it is this way. Warner On Apr 29, 2011, at 11:36 AM, Jayachandran C. wrote: > In sys/mips/include/_types.h, I see >=20 > | 119 typedef __int64_t __time_t; /* time()... */ >=20 > Which as far as I can see, is not right for the 32-bit ABIs. But this > definition has been there for a long time, so I would like to know if > there is any reason for this? >=20 > Since this is a user-visible type, changing it would break binary = compatibility. >=20 > Thanks, > JC. >=20 >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DD2906D8-811B-4CFB-B899-2AC88FF26720>