[tz] gcc 8 demanded patch (from NetBSD)
Brian.Inglis at SystematicSw.ab.ca
Thu May 11 15:02:26 UTC 2017
On 2017-05-10 10:35, Steve Allen wrote:
> 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.
...other than produce more "standards" which most governments, licensed
broadcasters, and commercial equipment designers selectively or totally
ignore when impractical or uneconomic.
Does or can anyone now use and trust broadcast time or frequency signals,
other than as low quality backup sources suitable for syncing clocks and
watches, for those who still like the familiarity of antiquated displays,
such as the politicians and judges who legislate "solar" civil time?
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
More information about the tz