From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 22 13:12:58 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2E29216A407; Thu, 22 Mar 2007 13:12:58 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from gateway.cybervisiontech.com.ua (gateway.cybervisiontech.com.ua [88.81.251.18]) by mx1.freebsd.org (Postfix) with ESMTP id DDF3813C45E; Thu, 22 Mar 2007 13:12:54 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from localhost (hq.cybervisiontech.com [127.0.0.1]) by gateway.cybervisiontech.com.ua (Postfix) with ESMTP id 3720DED501E; Thu, 22 Mar 2007 15:12:50 +0200 (EET) X-Virus-Scanned: amavisd-new at cybervisiontech.com Received: from gateway.cybervisiontech.com.ua ([127.0.0.1]) by localhost (hq.cybervisiontech.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WwNZ4-+OIjSX; Thu, 22 Mar 2007 15:12:44 +0200 (EET) Received: from [10.2.1.87] (rein.cybervisiontech.com.ua [10.2.1.87]) by gateway.cybervisiontech.com.ua (Postfix) with ESMTP id B3A4BED5010; Thu, 22 Mar 2007 15:12:44 +0200 (EET) Message-ID: <460280CF.2090200@icyb.net.ua> Date: Thu, 22 Mar 2007 15:12:47 +0200 From: Andriy Gapon User-Agent: Thunderbird 1.5.0.10 (X11/20070322) MIME-Version: 1.0 To: "Olson, Arthur David \(NIH/NCI\) [E]" References: <45FE9B11.5030909@icyb.net.ua> <46013D6F.4020704@icyb.net.ua> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: wollman@freebsd.org, freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: zdump on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2007 13:12:58 -0000 on 22/03/2007 15:06 Olson, Arthur David (NIH/NCI) [E] said the following: > Check the version of zdump in use with a... > zdump --version > ...command; starting with the February 2006 (8.1) version, output has been limited to run from the year -500 to the year 2500 by default. The range can be changed using the... > -c [loyear],hiyear > ...option. Thank you for the pointer! I guess it is a question of updating FreeBSD sources from upstream now: $ zdump --version zdump: @(#)zdump.c 7.31 > -----Original Message----- > From: Andriy Gapon [mailto:avg@icyb.net.ua] > Sent: Wednesday, March 21, 2007 10:13 AM > To: freebsd-amd64@freebsd.org; freebsd-stable@freebsd.org > Cc: wollman@freebsd.org; tz@lecserver.nci.nih.gov > Subject: Re: zdump on amd64 > > on 19/03/2007 16:15 Andriy Gapon said the following: >> Strange problem: >> $ uname -srm >> FreeBSD 6.2-RELEASE-p2 amd64 >> >> $ zdump -v EST >> EST Sun Jan 26 08:29:52 -219 UTC = Sun Jan 26 03:29:52 -219 EST isdst=0 >> gmtoff=-18000 >> EST Mon Jan 27 08:29:52 -219 UTC = Mon Jan 27 03:29:52 -219 EST isdst=0 >> gmtoff=-18000 >> EST Fri Jan 1 04:59:59 -219 UTC = Thu Dec 30 23:59:59 -219 EST isdst=0 >> gmtoff=-18000 >> EST Fri Jan 1 05:00:00 -219 UTC = Fri Jan 1 00:00:00 -219 EST isdst=0 >> gmtoff=-18000 >> ^C > ... >> Before each ^C zdump was hanging eating 100% CPU. >> Something about 64-bitness ? > > Hmm. I hurried to assert that it was hanging, it was actually searching. > It seems that zdump -v algorithm is to start with minimal time_t > possible (large negative number in our case) and to go to maximum time_t > using 12 hours increments and doing certain checks for DST jumps. > Well, with 64-bit time_t start date is somewhere 200 milliard (10^9) > years ago and end date is the same in the future, so iteration over > those years takes quite a while. And tz db doesn't contain anything > useful for too distant years anyway. > > I think that zdump should be optimized to limit its search range. At the > very least for the start point - what is current estimate of the age of > our Universe :-) > > -- Andriy Gapon