From: Florian Weimer <fweimer@redhat.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
libc-alpha@sourceware.org, Bruno Haible <bruno@clisp.org>
Subject: Re: [PATCH] time: Use CLOCK_REALTIME for time (BZ #30200)
Date: Wed, 08 Mar 2023 09:59:47 +0100 [thread overview]
Message-ID: <874jqvty7w.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <e0b0f815-d344-38cb-99e0-1278b7068197@cs.ucla.edu> (Paul Eggert's message of "Tue, 7 Mar 2023 21:51:00 -0800")
* Paul Eggert:
> On 2023-03-07 04:07, Florian Weimer via Libc-alpha wrote:
>> Probably RESOLVED/MOVED because we get whatever time the kernel
>> provides. It seems a deliberate kernel decision to me.
>
> For my own information, is 'time' the only standard function that uses
> a clock other than CLOCK_REALTIME and so can be out-of-sync with
> timespec_get? What about gettimeofday, futimens with UTIME_NOW, or
> timestamps set by modifying files?
Even if the same underlying clock is used, rounding may cause interface
which use different precision for the fractional seconds part to report
different integral seconds. The standard does not require rounding
towards minus infinity.
Thanks,
Florian
next prev parent reply other threads:[~2023-03-08 8:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 16:03 Adhemerval Zanella
2023-03-07 11:11 ` Florian Weimer
2023-03-07 11:45 ` Adhemerval Zanella Netto
2023-03-07 11:51 ` Florian Weimer
2023-03-07 11:57 ` Adhemerval Zanella Netto
2023-03-07 12:07 ` Florian Weimer
2023-03-08 5:51 ` Paul Eggert
2023-03-08 8:59 ` Florian Weimer [this message]
2023-03-08 23:08 ` Paul Eggert
2023-03-08 16:23 ` Bruno Haible
2023-03-08 16:57 ` Adhemerval Zanella Netto
2023-03-08 17:09 ` Florian Weimer
2023-03-08 17:46 ` Adhemerval Zanella Netto
2023-03-08 17:44 ` Bruno Haible
2023-03-08 17:50 ` Adhemerval Zanella Netto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874jqvty7w.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=bruno@clisp.org \
--cc=eggert@cs.ucla.edu \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).