From owner-freebsd-arm@FreeBSD.ORG  Fri May 12 03:32:36 2006
Return-Path: <owner-freebsd-arm@FreeBSD.ORG>
X-Original-To: arm@freebsd.org
Delivered-To: freebsd-arm@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id B9F8C16A425
	for <arm@freebsd.org>; Fri, 12 May 2006 03:32:36 +0000 (UTC)
	(envelope-from imp@bsdimp.com)
Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A620143DAE
	for <arm@freebsd.org>; Fri, 12 May 2006 03:32:30 +0000 (GMT)
	(envelope-from imp@bsdimp.com)
Received: from localhost (localhost.village.org [127.0.0.1] (may be forged))
	by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id k4C3TsTV054086
	for <arm@freebsd.org>; Thu, 11 May 2006 21:29:55 -0600 (MDT)
	(envelope-from imp@bsdimp.com)
Date: Thu, 11 May 2006 23:30:03 -0400 (EDT)
Message-Id: <20060511.233003.87762623.imp@bsdimp.com>
To: arm@freebsd.org
From: "M. Warner Losh" <imp@bsdimp.com>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: 
Subject: time_t 64 bits?
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting FreeBSD to the StrongARM Processor <freebsd-arm.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
	<mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
	<mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 May 2006 03:32:37 -0000

John Baldwin just asked me why time_t is 32 bits on arm.  Is there any
reason for it?  Can we change it to 64 bits?  Would this cause
problems for our users?

Warner