From owner-freebsd-alpha  Tue Dec 22 06:12:27 1998
Return-Path: <owner-freebsd-alpha@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id GAA21168
          for freebsd-alpha-outgoing; Tue, 22 Dec 1998 06:12:27 -0800 (PST)
          (envelope-from owner-freebsd-alpha@FreeBSD.ORG)
Received: from mail.sat.t.u-tokyo.ac.jp (dryad.sat.t.u-tokyo.ac.jp [133.11.156.10])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA21163
          for <freebsd-alpha@FreeBSD.ORG>; Tue, 22 Dec 1998 06:12:25 -0800 (PST)
          (envelope-from simokawa@sat.t.u-tokyo.ac.jp)
Received: from ett.sat.t.u-tokyo.ac.jp (ett.sat.t.u-tokyo.ac.jp [133.11.156.43])
	by mail.sat.t.u-tokyo.ac.jp (8.8.6/3.4Wbeta6-SAT1.0) with ESMTP id XAA27154;
	Tue, 22 Dec 1998 23:12:21 +0900 (JST)
	(envelope-from simokawa@sat.t.u-tokyo.ac.jp)
Received: from localhost by ett.sat.t.u-tokyo.ac.jp (8.8.8/sat-V0.6)
	id XAA04492; Tue, 22 Dec 1998 23:12:21 +0900 (JST)
To: kaleb@ics.com
Cc: freebsd-alpha@FreeBSD.ORG
Subject: Re: time_t and clock_t
In-Reply-To: Your message of "Tue, 22 Dec 1998 08:48:26 -0500"
	<367FA329.7566F4CF@ics.com>
References: <367FA329.7566F4CF@ics.com>
X-Face: OE([KxWyJI0r[R~S/>7ia}SJ)i%a,$-9%7{*yihQk|]gl}2p#"oXmX/fT}Bn7:#j7i14gu$
 jgR\S*&C3R/pJX<mI-4Z8'mqt1R'CjWdw-xqVoilv`\JgZcquM5oVuO^<vt/~051rCDM(`{rM~?{Ok
 r,XC+}Ycm9IJO)odT*-0nyJjBJYzL{GsZ
X-Mailer: Mew version 1.93 on XEmacs 21.0 (Poitou)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <19981222231220B.simokawa@sat.t.u-tokyo.ac.jp>
Date: Tue, 22 Dec 1998 23:12:20 +0900
From: Hidetoshi Shimokawa <simokawa@sat.t.u-tokyo.ac.jp>
X-Dispatcher: imput version 980905(IM100)
Lines: 32
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

kaleb> >  According to /usr/include/machine/ansi.h, time_t and clock_t are "int" on
kaleb> > alpha and "long" on i386 respectively. I know "int" on alpha and "long" on
kaleb> > i386 are same size 32bit, but I don't think it's resonable that time_t on
kaleb> > alpha is "int". 
kaleb> 
kaleb> FWIW, time_t and clock_t are also int on Digital Unix.
kaleb>
kaleb> > At least, "tv_sec" part of timeval is declared as "long".
kaleb> > Why don't we change time_t as "long"? 
kaleb> 
kaleb> Are time_t and clock_t supposed to be 32-bit types? I'll have to check
kaleb> my POSIX specs when I get to work.

I don't have POSIX specs, so please let me know what specs says.
In linux kernel, linux/include/asm-alpha/posix_types.h defines:
typedef long            __kernel_time_t;
and linux/include/linux/types.h defines:
typedef __kernel_time_t         time_t;

kaleb> > It should make our life easier.
kaleb> 
kaleb> How so? Using the right type name consistently should be all that's
kaleb> necessary to make life easier, right?

Some (old) programs includes a line something like:
long time();
and fails to be compiled. Of course, we should delete the line.
(I found some during package building)

/\ Hidetoshi Shimokawa
\/  simokawa@sat.t.u-tokyo.ac.jp
PGP public key: finger -l simokawa@sat.t.u-tokyo.ac.jp

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message