public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: Paul Eggert <eggert@cs.ucla.edu>, DJ Delorie <dj@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [swbz 29035] mktime vs non-DST
Date: Thu, 18 Aug 2022 00:05:36 -0400	[thread overview]
Message-ID: <55d6517d-5079-cde7-5934-ca3c704753b4@redhat.com> (raw)
In-Reply-To: <dbd35095-f4e6-9153-2528-3c7d68bfa2fb@cs.ucla.edu>

On 8/17/22 23:16, Paul Eggert wrote:
> On 8/17/22 19:37, Carlos O'Donell wrote:
>> The mktime() interface has been around for a long time and users do
>> not expect and have noticed the semantic changes we are seeing here
>> today.
> 
> The semantic changes that bother users boil down to the following:
> glibc mktime returns -1 when users specify impossible is_dst flags,
> whereas mktime used to succeed. That problem is fixed in Gnulib.

Right.

> The only disagreement between Gnulib and old (2.28) glibc in this
> area, is in relatively obscure cases where we have not seen any bug
> reports, and in these cases old glibc mostly gets it wrong (for
> example, see my previous email), whereas Gnulib mostly gets it right.
> Let's stick with the Gnulib behavior here.
 
What I'd like to see here as an outcome is a broader battery of tests in
glibc that cover the mktime() behaviour we want to support. We'll work on that
and review the recommended gnulib changes.

We have also seen a somewhat odd use of mktime() to detect DST transitions that
DJ and I need to audit and verify against the changes you have implemented in
gnulib.

Thanks for the quick comments. I think the next step is with us to do more
testing.

-- 
Cheers,
Carlos.


  reply	other threads:[~2022-08-18  4:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-17 21:18 DJ Delorie
2022-08-17 21:50 ` Carlos O'Donell
2022-08-17 23:10 ` Paul Eggert
2022-08-18  1:39   ` DJ Delorie
2022-08-18  2:37     ` Carlos O'Donell
2022-08-18  3:16       ` Paul Eggert
2022-08-18  4:05         ` Carlos O'Donell [this message]
2022-08-18 21:17       ` DJ Delorie
2022-08-18 21:57         ` Paul Eggert
2022-08-18 22:40           ` DJ Delorie
2022-08-18 22:58             ` Paul Eggert
2022-08-19 18:15               ` DJ Delorie
2022-08-19 22:04                 ` Paul Eggert
2022-08-18  3:02     ` Paul Eggert
2022-09-08 20:25   ` DJ Delorie

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=55d6517d-5079-cde7-5934-ca3c704753b4@redhat.com \
    --to=carlos@redhat.com \
    --cc=dj@redhat.com \
    --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).