Lines Matching refs:leap
35 The number of leap seconds for which data entries are stored
96 by time(2)) at which a leap second occurs or at which the leap second
98 correction, which is the total number of leap seconds to be applied
101 denotes one leap second, either positive or negative, except that if
103 pair denotes the leap second table's expiration time. Each leap
104 second is at the end of a UTC calendar month. The first leap second
105 has a nonnegative occurrence time, and is a positive leap second if
106 and only if its correction is positive; the correction for each leap
107 second after the first differs from the previous leap second by
108 either 1 for a positive leap second, or -1 for a negative leap
109 second. If the leap second table is empty, the leap-second
111 before the first occurrence time, the leap-second correction is zero
147 eight bytes are used for each transition time or leap second time.
173 For version-4-format TZif files, the first leap second record can have
175 TZif file at the start. Also, if two or more leap second transitions
177 the last entry denotes the expiration of the leap second table instead
178 of a leap second; timestamps after this expiration are unreliable in
179 that future releases will likely add leap second entries after the
180 expiration, and the added leap seconds will change how post-expiration
193 version 4 file only if its leap second table either expires or is
206 When a TZif file contains a leap second table expiration time, TZif
224 When a positive leap second occurs, readers should append an extra
225 second to the local minute containing the second just before the leap
227 seconds, the leap second occurs earlier than the last second of the
279 conformance to RFC 8536, reject version 4 files whose leap second
326 * Some readers generate ambiguous timestamps for positive leap seconds
329 leap second 78796801 (1972-06-30 23:59:60 UTC), some readers will map
334 offsets since leap seconds were introduced in 1972.