From owner-freebsd-mips@FreeBSD.ORG  Fri Apr 29 20:09:13 2011
Return-Path: <owner-freebsd-mips@FreeBSD.ORG>
Delivered-To: freebsd-mips@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 5E1C21065670;
	Fri, 29 Apr 2011 20:09:13 +0000 (UTC)
	(envelope-from c.jayachandran@gmail.com)
Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com
	[209.85.212.54])
	by mx1.freebsd.org (Postfix) with ESMTP id BAFCF8FC0C;
	Fri, 29 Apr 2011 20:09:12 +0000 (UTC)
Received: by vws18 with SMTP id 18so4019787vws.13
	for <multiple recipients>; Fri, 29 Apr 2011 13:09:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:cc:content-type
	:content-transfer-encoding;
	bh=GOIstGUrcs300kWlBCmXWiTwEU8+FA9Uu9gRIYkHdw4=;
	b=cMbpI2kwPHOUE2MYrtIJsrDLHyibtyb17vV45pBt6hi2jnJSJlxdqJHOCiNmz+IC+7
	DAQvhtiBVyFa8XqkY48dLBfVYhJZvC8sSwjQ3k8UXK5WXd7vl6EJvHKp+jG8ROuwNNIR
	IhaIpGw0n97TXe5cXIOpefDuPFYwutzLoXRx8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:content-transfer-encoding;
	b=hLd7VsdNrWdsBAr1LU6XFvebQnUfvjxAKM1sRwM/fqL0qxmn1e8Tw86kjXQqysXC/t
	YMxKiNL8Ld5BhXPBqj7RQyCN2bgylQy4L8/5UTdPJNJJ54EuKQc/evMaZe59qEFOlk/B
	fgTegVxccjRPpl9chgmEQBuqRkFjcEfuo+708=
MIME-Version: 1.0
Received: by 10.52.187.202 with SMTP id fu10mr2217312vdc.127.1304107752078;
	Fri, 29 Apr 2011 13:09:12 -0700 (PDT)
Received: by 10.52.182.105 with HTTP; Fri, 29 Apr 2011 13:09:12 -0700 (PDT)
In-Reply-To: <DD2906D8-811B-4CFB-B899-2AC88FF26720@bsdimp.com>
References: <BANLkTimdbgabRCBbdjR1L45DtkETDT1UNw@mail.gmail.com>
	<DD2906D8-811B-4CFB-B899-2AC88FF26720@bsdimp.com>
Date: Sat, 30 Apr 2011 01:39:12 +0530
Message-ID: <BANLkTi=vdkPNGwpi=CBNecMjbS+=S44suA@mail.gmail.com>
From: "Jayachandran C." <c.jayachandran@gmail.com>
To: Warner Losh <imp@bsdimp.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: freebsd-mips@freebsd.org
Subject: Re: 64 bit time_t in 32 bit ABI?
X-BeenThere: freebsd-mips@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting FreeBSD to MIPS <freebsd-mips.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-mips>,
	<mailto:freebsd-mips-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-mips>
List-Post: <mailto:freebsd-mips@freebsd.org>
List-Help: <mailto:freebsd-mips-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-mips>,
	<mailto:freebsd-mips-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Apr 2011 20:09:13 -0000

On Sat, Apr 30, 2011 at 12:54 AM, Warner Losh <imp@bsdimp.com> wrote:
> I thought we made all new architectures adopt a 32-bit time_t and that's =
why it is this way.

Although it is not required by standard, having time_t as long is (in
my opinion) would be the least surprising implementation. Having it
'long long' on 32-bit will avoid the 2038 issue, but it also makes us
incompatible with other platforms and might trip up some programs.

That said, if this is a decision that has been taken, we will abide by that=
.

JC.

> Warner
>
> On Apr 29, 2011, at 11:36 AM, Jayachandran C. wrote:
>
>> In sys/mips/include/_types.h, I see
>>
>> | 119 typedef __int64_t =A0 =A0 =A0 __time_t; =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 /* time()... */
>>
>> 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?
>>
>> Since this is a user-visible type, changing it would break binary compat=
ibility.
>>
>> Thanks,
>> JC.