From owner-freebsd-arch Sat Jun 2 12:51:59 2001 Delivered-To: freebsd-arch@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 261A037B423; Sat, 2 Jun 2001 12:51:54 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f52Jpe139983; Sat, 2 Jun 2001 21:51:40 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: obrien@FreeBSD.ORG Cc: Matt Dillon , David Wolfskill , arch@FreeBSD.ORG Subject: Re: time_t definition is worng In-Reply-To: Your message of "Sat, 02 Jun 2001 12:47:32 PDT." <20010602124732.F31257@dragon.nuxi.com> Date: Sat, 02 Jun 2001 21:51:39 +0200 Message-ID: <39981.991511499@critter> From: Poul-Henning Kamp 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 In message <20010602124732.F31257@dragon.nuxi.com>, "David O'Brien" writes: >On Sat, Jun 02, 2001 at 10:39:09AM -0700, Matt Dillon wrote: >> Consistency is best, but breaking IA32 to match the already broken >> Alpha port is the wrong solution. For consistency we should match > >Why is the Alpha port broken? time_t is 32-bits without question. Thus >it must be an `int' on Alpha, IA-64, and sparc64. Uhm, time_t must be signed and at least 32 bits. It would be neat if all platforms had it longer than 32 bits in the next decade some time. >> Certain core types like time_t >> have serious limitations when declared as a fixed width type (int >> nowadays). long is the perfect solution and you just blew that all to >> hell with this commit. > >I am more than willing to define time_t as `long long' so it is 64-bits >across the board. We'll have to do this before 2038 anyway... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message