Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 02 Jun 2001 21:51:39 +0200
From:      Poul-Henning Kamp <phk@critter.freebsd.dk>
To:        obrien@FreeBSD.ORG
Cc:        Matt Dillon <dillon@earth.backplane.com>, David Wolfskill <david@catwhisker.org>, arch@FreeBSD.ORG
Subject:   Re: time_t definition is worng 
Message-ID:  <39981.991511499@critter>
In-Reply-To: Your message of "Sat, 02 Jun 2001 12:47:32 PDT." <20010602124732.F31257@dragon.nuxi.com> 

next in thread | previous in thread | raw e-mail | index | archive | help
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39981.991511499>