From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id YK5KHy1lYGIKNQEAbAwnHQ (envelope-from ) for ; Wed, 20 Apr 2022 21:55:25 +0200 Received: from aspmx1.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id EN5mHi1lYGKgDQEAG6o9tA (envelope-from ) for ; Wed, 20 Apr 2022 21:55:25 +0200 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 2489719D36 for ; Wed, 20 Apr 2022 21:55:25 +0200 (CEST) Received: from localhost ([::1]:43246 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nhGQ7-0006un-FF for larch@yhetil.org; Wed, 20 Apr 2022 15:55:23 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:42062) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nhG22-000614-SD; Wed, 20 Apr 2022 15:30:30 -0400 Received: from fencepost.gnu.org ([2001:470:142:3::e]:43250) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nhG21-0005Qt-Lb; Wed, 20 Apr 2022 15:30:29 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=ii4iG9/zZJp/M1A5E/sXfZAJ4V0ONgog6zZ7DkyfZjE=; b=RHvE9VLYvGWh bnTzrH9PY0yHOG1puj3+jWa0Ei++9zNl58p6fRNgo8+bYBxLuCY3/TXPMyDIp6InJcszzycv40Xuc fLE9hFGPMbZEf4K+bPtWiRVgjN/a7iAy+VimDlhfw1yfSXyt6H7lMsy4XFWRLyRCGFdH9gnFZY2vR CCsgHfQuvkuoapUCLjlCcCLPDXmKQfJPqnxgFgjXuuxHjT4OEqdPTSIq9iJ/Eaub9xoS6BHvjwpyI h8uLWAZdktVP/qgXnypwiqImbE3hou996XKyDNyoWD3Q847UI5NMMg6SRByZmGxMHIIYNhkcF3Z2R z/iDUkLHxsqAH58t1sYVLA==; Received: from [87.69.77.57] (port=2363 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nhG21-0001nB-4z; Wed, 20 Apr 2022 15:30:29 -0400 Date: Wed, 20 Apr 2022 22:30:21 +0300 Message-Id: <83czhbsgc2.fsf@gnu.org> From: Eli Zaretskii To: Paul Eggert In-Reply-To: (message from Paul Eggert on Wed, 20 Apr 2022 12:23:43 -0700) Subject: Re: bug#54764: encode-time: make DST and TIMEZONE fields of the list argument optional ones References: <5ed963b2-3fa8-48d8-627e-bc0571d15b43@gmail.com> <149de00f-115b-5367-414f-c7700ef8966b@cs.ucla.edu> <2dd15844-01b3-0144-740c-185ec8488a81@cs.ucla.edu> <4a23f3a4-fe8f-d396-49d8-10034803be63@gmail.com> <52fb10fb-892a-f273-3be8-28793f27e204@cs.ucla.edu> <5cd820d4-ae67-43d4-9e63-c284d51ff1e4@gmail.com> <83tuapvcxs.fsf@gnu.org> <6efc5d24-34a2-fd30-cd20-fe4ac3e48310@cs.ucla.edu> <83fsm8tdzl.fsf@gnu.org> <9e4781b2-2ffa-b1ce-09b4-ead82cad9038@cs.ucla.edu> <83ilr3siku.fsf@gnu.org> <4e41671c-fae8-61c4-845c-4c7ba4317e88@cs.ucla.edu> <83fsm7sh2s.fsf@gnu.org> X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: bug-gnulib@gnu.org, manikulin@gmail.com, emacs-orgmode@gnu.org, 54764@debbugs.gnu.org Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Migadu-Flow: FLOW_IN X-Migadu-To: larch@yhetil.org X-Migadu-Country: US ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1650484525; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=ii4iG9/zZJp/M1A5E/sXfZAJ4V0ONgog6zZ7DkyfZjE=; b=OpCta4ySkagzxbkgH0Q900qkGZnGhfm+rb/2R13pZzF9/hSlm3hqURqhhUj19kmYXKcOIE AcMs53ZOlM2LbsyarXzBKF7qw4IFRtYgzy+6TY2mkDQXwO3STIEM12fE7UK6ObLkJxHBDc De5APDkUwVenZnnOlMB4ER5CYM9oYZPAO6TCDJYPWFdR4vwq8jyLGL+BUUUXg9CUyOk2eT vSap8pgiel5GWxGzifSo88Fz6aLk5NKti4Rdj3Q8Wds5NMn9agIV6PqTf0P+bpBApYXtAw HTZiGuW7t7fMg4mZ6qHDpkOs/bI5YJo+6I4WM0YrkohNdKQ3fvflIaA/3s1+YQ== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1650484525; a=rsa-sha256; cv=none; b=RbIKVG/lJ8pkXYQ4f9arivk6ULKgr5VYU+HFIt1vs1j7HZ9NBQI1znML2ebhplUjowvvCY fKevCznYvLa8z5BZYAMwh4UYKIqnunCFprFwoJQGDScxfPdN23u5Slvezsrtk2QUVhPjaE R81YvBkaJpN78xAcU6SJYRIPo1FCS7K/RHjEJhv5bk/TmCyjUdisRC6lGcr+8J0rzxOWHz NQPC/RqVyb6E60hdh7+3eJfNyU2dgkRLpuJ3vU1OIHnudNsLrxetMfOK6s5YSO8rVF5vhz P58TFo82S+Lo0HIIXzNR/WNgoeOfNCS5AwX2OcYSlHcynpt3GIkuMbE4OxvMJA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gnu.org header.s=fencepost-gnu-org header.b=RHvE9VLY; dmarc=pass (policy=none) header.from=gnu.org; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" X-Migadu-Spam-Score: -5.24 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gnu.org header.s=fencepost-gnu-org header.b=RHvE9VLY; dmarc=pass (policy=none) header.from=gnu.org; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" X-Migadu-Queue-Id: 2489719D36 X-Spam-Score: -5.24 X-Migadu-Scanner: scn1.migadu.com X-TUID: YwfvcRZX8wuB > Date: Wed, 20 Apr 2022 12:23:43 -0700 > Cc: manikulin@gmail.com, emacs-orgmode@gnu.org, 54764@debbugs.gnu.org, > bug-gnulib@gnu.org > From: Paul Eggert > > On 4/20/22 12:14, Eli Zaretskii wrote: > > Sorry, my bad. The result is the same, but I do get printouts. What > > do you want to know or see from there? > > I want to see what the current_timespec's resolution is, which we should > be able to tell from the debugging output. For example, on my Solaris 10 > sparc platform the command 'gltests/test-gettime-res x' outputs: > > gettime_res returned 200 ns > time = 1650482432.256445600 > time = 1650482432.256460600 > time = 1650482432.256464400 > time = 1650482432.256468200 > time = 1650482432.256471400 > time = 1650482432.256474600 > time = 1650482432.256478000 > time = 1650482432.256481200 > time = 1650482432.256484800 > ... > > and these timestamps say that with very high probability > current_timespec's clock resolution is indeed 200 ns. I see the time samples change in jumps of 15 msec. Which is expected on MS-Windows, given the scheduler time tick, but what does that have to do with the system's time resolution? And how is the 0.625 msec number reported by the program obtained from those samples?