[tz] gcc 8 demanded patch (from NetBSD)

Steve Allen sla at ucolick.org
Wed May 10 16:35:42 UTC 2017

On Wed 2017-05-10T11:31:45 +0700, Robert Elz hath writ:
>   | Admittedly, there has never been a double leap,
> There never will be, that "double leap second" myth was born from a
> misunderstanding about "there may be two leap seconds in one year"
> (which meant one at the end of June, and one at the end of December,
> but was interpreted to mean that there might be two at the same time.)
> Any code, anywhere, that is allowing for either 56, 57, 0, 1, 2
> or 57, 58, 59, 60, 61, 0, 1, 2  should simply be blast from orbit.

Never say never.

In 1969 CCIR Interim Working Party 7/1 produced CCIR Plenary Assembly
Document VII/1008, and that allowed for multiple leap seconds.  The
change to remove multiple leap seconds from that document was made on
1970-02-03 in the open discussion during the 13th plenary session of
12th Plenary Assembly of the CCIR.  Thus it became CCIR Recommendation
460, now evolved into the current version ITU-R TF.460-6.

It is very hard to say what the ITU-R might or might not do.

Steve Allen                    <sla at ucolick.org>              WGS-84 (GPS)
UCO/Lick Observatory--ISB 260  Natural Sciences II, Room 165  Lat  +36.99855
1156 High Street               Voice: +1 831 459 3046         Lng -122.06015
Santa Cruz, CA 95064           http://www.ucolick.org/~sla/   Hgt +250 m

More information about the tz mailing list