From owner-freebsd-arch Fri Oct 26 19:48:46 2001 Delivered-To: freebsd-arch@freebsd.org Received: from falcon.prod.itd.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by hub.freebsd.org (Postfix) with ESMTP id EFF0D37B401; Fri, 26 Oct 2001 19:48:43 -0700 (PDT) Received: from dialup-209.245.143.103.dial1.sanjose1.level3.net ([209.245.143.103] helo=mindspring.com) by falcon.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 15xJWd-0007Hb-00; Fri, 26 Oct 2001 19:48:43 -0700 Message-ID: <3BDA20C0.ED922810@mindspring.com> Date: Fri, 26 Oct 2001 19:49:36 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin Cc: Matthew Dillon , arch@FreeBSD.ORG, Peter Wemm , Poul-Henning Kamp , Bakul Shah , Mike Smith , Dag-Erling Smorgrav Subject: Re: 64 bit times revisited.. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG John Baldwin wrote: > You did read the e-mail from Garrett where either SUS or POSIX one requires > time_t to fit in a long? I.e. sizeof(time_t) <= sizeof(long). The basis for this is the atomic type argument. We already violate this one (in spades) for the off_t definition, which has the same requirement, yet is a "long long" on FreeBSD. Just food for thought... if the standard doesn't cover the case, it doesn't automatically mean that compliance is a good idea. We could always hack the compiler for an 128 bit "atomic" type, e.g. "very long long" or "long long long", and treat time_t the same way we treat off_t: with a nod and a wink to the standard, but incomplete actualtechnical compliance, if you were a C language lawyer... -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message