From owner-freebsd-hackers Mon Nov 19 17:57:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by hub.freebsd.org (Postfix) with ESMTP id 6B86837B416 for ; Mon, 19 Nov 2001 17:57:16 -0800 (PST) Received: (qmail 32421 invoked from network); 20 Nov 2001 01:57:14 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 20 Nov 2001 01:57:14 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20011119200200.A33416@ussenterprise.ufp.org> Date: Mon, 19 Nov 2001 17:57:04 -0800 (PST) From: John Baldwin To: Leo Bicknell Subject: Re: Ok, who broke timed? Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 20-Nov-01 Leo Bicknell wrote: > On Mon, Nov 19, 2001 at 04:51:29PM -0800, John Baldwin wrote: >> That looks very promising indeed. Hrmm. I should go see if NetBSD has >> fixed >> this. I guess having timeval be different sizes on different archs is a bit >> of >> a pain. :( Perhaps it should use uint32_t? Or perhaps struct tsp should >> use >> its own variant of timeval with uint32_t or some such. Ugh. > > If timeval is different sizes on different archs then I would > recomend the work be done take it to 64 bits, not 32. It fixes a > problem in about 30 years. :-) We'll cross that bridge when it comes to it, right now we need to not break binary compatibility with all those existing 4.x machines out there right now. Also, NetBSD used int32_t to be consistent. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message