From owner-freebsd-arch@FreeBSD.ORG  Fri Nov 14 11:41:21 2003
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 692B716A4CE
	for <freebsd-arch@freebsd.org>; Fri, 14 Nov 2003 11:41:21 -0800 (PST)
Received: from gw.celabo.org (gw.celabo.org [208.42.49.153])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9E57743F75
	for <freebsd-arch@freebsd.org>; Fri, 14 Nov 2003 11:41:20 -0800 (PST)
	(envelope-from nectar@celabo.org)
Received: from madman.celabo.org (madman.celabo.org [10.0.1.111])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client CN "madman.celabo.org", Issuer "celabo.org CA" (verified OK))
	by gw.celabo.org (Postfix) with ESMTP id 330F0548A5
	for <freebsd-arch@freebsd.org>; Fri, 14 Nov 2003 13:41:20 -0600 (CST)
Received: by madman.celabo.org (Postfix, from userid 1001)
	id C7E8C6D455; Fri, 14 Nov 2003 13:41:19 -0600 (CST)
Date: Fri, 14 Nov 2003 13:41:19 -0600
From: "Jacques A. Vidrine" <nectar@FreeBSD.org>
To: freebsd-arch@freebsd.org
Message-ID: <20031114194119.GA94198@madman.celabo.org>
Mail-Followup-To: "Jacques A. Vidrine" <nectar@FreeBSD.org>,
	freebsd-arch@freebsd.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Url: http://www.celabo.org/
User-Agent: Mutt/1.5.4i-ja.1
Subject: __TIME_MIN/__TIME_MAX
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussion related to FreeBSD architecture
	<freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Nov 2003 19:41:21 -0000

In at least one place in libc, it is necessary to range check a time_t
value.  One most platforms, time_t has the same range as `int', but
on at least amd64, it has a larger range.  Any objections to adding
definitions of __TIME_MIN and __TIME_MAX to sys/${arch}/_limits.h?

I could just do the usual check for lossage after casting, except that
in theory time_t could be a floating-point value (but not in reality
in FreeBSD).  It seems cleaner to me to have an explicit range.

Cheers,
-- 
Jacques Vidrine   NTT/Verio SME      FreeBSD UNIX       Heimdal
nectar@celabo.org jvidrine@verio.net nectar@freebsd.org nectar@kth.se