From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id DE0A53858D3C for ; Mon, 14 Feb 2022 21:33:40 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org DE0A53858D3C Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1644874420; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=wjE/oUIwR8c1T9kY3T/t9Czl5X3LH4/sm1Ha4XHD4cI=; b=ZcgpP9PHPwMH4j67yiaYt6wkXwuybVL+fcjxaD6iZdIGOAH53jZRW4CmV33jHzJnglAsTH JtDrN86vAZq8HhpQB9oJtzdCzs3trqEDXx8K4HMEuGpnDZmVx4ZndUGg2EJSC12DZigZ66 fv79FWI03OKkFVqqgNv2AA/GrOkewYw= Received: from mail-yb1-f198.google.com (mail-yb1-f198.google.com [209.85.219.198]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-255-6PRPQKldMNS06ZbwUKZY1Q-1; Mon, 14 Feb 2022 16:33:37 -0500 X-MC-Unique: 6PRPQKldMNS06ZbwUKZY1Q-1 Received: by mail-yb1-f198.google.com with SMTP id s133-20020a252c8b000000b0062112290d0bso21577771ybs.23 for ; Mon, 14 Feb 2022 13:33:37 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=wjE/oUIwR8c1T9kY3T/t9Czl5X3LH4/sm1Ha4XHD4cI=; b=gMfB8GWSd+ULiIidor6PqtM/e945JyM0CODGDI6EuFGuhcUnxUwSSA4pXQ4okbgVIN ejVJeT/5zeNFWzzMg0C0PeBiJB2ddd/hLdv+q1jC9I7KqblWyljc2rFJ09hzQicWaABo szGt6jeXTd0ZEHIQdqknFOZuaRdPM1KcQCD8lji4BBCr/FLhkGZ1PEEv+O1nWDqNJVou cCrrWeYMo/yEfBrfMD0s/h+CPW8OeSN56dK2q5DzLO2Jmn87WbREVrzrQy7IrCWAKw85 39bn/qh19GhDD9U7uIBByLBz4gwEX8e7iySEFLmocoFwfDaLFUrgWGpZzR6NebxlgHMg Y9Kg== X-Gm-Message-State: AOAM533p4GZlVnuUnqN8bkv99dJVXVCYPW7a9SWzQUvZ6Q2eEbHRRqgS HPsKSY9MzNSPlxkOzZ1fK/cHzgX9koVk8jq5EpCcfMcP7lLo4iXbbFa47crYKLhDqpFCdoNyO3Y 2TPLUJbKLjuQDqmYCheqF25RPmLsfGFY= X-Received: by 2002:a5b:78f:: with SMTP id b15mr1057344ybq.514.1644874416472; Mon, 14 Feb 2022 13:33:36 -0800 (PST) X-Google-Smtp-Source: ABdhPJyIt49vSXzwOOHbTtaaRnU/9eQ5ODT6SOd5dDiDB9CT7DqKxJ+zXp584vmkswr5giz+E++L2QD4GPb9ucTiQmE= X-Received: by 2002:a5b:78f:: with SMTP id b15mr1057333ybq.514.1644874416274; Mon, 14 Feb 2022 13:33:36 -0800 (PST) MIME-Version: 1.0 References: <758cfb47-ac13-fb88-877e-63a1d4327429@SystematicSw.ab.ca> In-Reply-To: From: Jeff Johnston Date: Mon, 14 Feb 2022 16:33:25 -0500 Message-ID: Subject: Re: Support non-POSIX TZ strings To: Newlib Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=jjohnstn@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com X-Spam-Status: No, score=-4.8 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, HTML_MESSAGE, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: newlib@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Newlib mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Feb 2022 21:33:42 -0000 On Mon, Feb 14, 2022 at 3:46 PM Brian Inglis < Brian.Inglis@systematicsw.ab.ca> wrote: > On 2022-02-14 12:58, jdoubleu wrote: > > On 22-02-14 10:10-0700, Brian Inglis wrote: > > >> [..] but we should start with the actual POSIX spec under TZ > > > Yes, that is exactly what I meant: Newlib supporting the <> (angle > > brackets) syntax. > > I didn't know that it was actually part of POSIX spec, since so many > > libs actually don't implement it. > > Most should have by now if maintained: we should be a laggard! ;^> > > >> The BSD or TZcode implementations could probably be adapted [..] > > > It looks like the TZcode implementation by Paul Eggert uses a different > > approach to parsing the strings, than the current implementation in > > newlib > > ( > https://sourceware.org/git/?p=newlib-cygwin.git;a=blob;f=newlib/libc/time/tzset_r.c). > > > I'm not sure, if you want to copy the code over or use changes by e.g. > > Earle F. Philhower from > > https://github.com/earlephilhower/newlib-xtensa/pull/14. > > Because of the above question, I'm not sure how to continue on this. I > > would like to contribute myself and submit an implementation, but I'll > > wait for feedback by other maintainers, first. > > Upstream sources like BSDs or TZcode official reference implementations > are normally preferred because they are feature complete, regularly > maintained, feature test and standards compliant, vulnerabilities > checked, issues reported, and promptly fixed. > > I checked the BSDs and they seem to have adopted or adapted the TZcode > official reference implementation, so I am not sure from where it may > have been adopted, or whether it is original: the maintainer Jeff > Johnson may remember. > Unfortunately, I do not remember the exact details from back then. With no license header, it means it was written by Cygnus/Red Hat. > I also wonder if the GMT defaults should be updated to UTC. > > -- > Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada > > This email may be disturbing to some readers as it contains > too much technical detail. Reader discretion is advised. > [Data in binary units and prefixes, physical quantities in SI.] > >