| /third_party/tzdata/ |
| D | leapseconds | 1 # Allowance for leap seconds added to each time zone file.
6 # NIST/IERS format leap-seconds.list file, which can be copied from
7 # <https://hpiers.obspm.fr/iers/bul/bulc/ntp/leap-seconds.list>
9 # <ftp://ftp.boulder.nist.gov/pub/time/leap-seconds.list>.
10 # For more about leap-seconds.list, please see
12 # <https://www.eecis.udel.edu/~mills/leap.html>.
14 # The rules for leap seconds are specified in Annex 1 (Time scales) of:
20 # periodically uses leap seconds to keep UTC to within 0.9 s of UT1
22 # and publishes leap second data in a copyrighted file
24 # See: Levine J. Coordinated Universal Time and the leap second.
[all …]
|
| D | time2posix.3.txt | 18 time_t values cannot include leap seconds and, therefore, that the
19 system time must be adjusted as each leap occurs.
21 If the time package is configured with leap-second support enabled,
23 increase over leap events (as a true "seconds since..." value). This
25 net number of leap seconds inserted since the Epoch.
34 will typically not handle intervals over leap seconds correctly.
39 base changes that would have taken place on a POSIX system as leap
46 well-behaved: for a positive leap second hit the result is not unique,
47 and for a negative leap second hit the corresponding POSIX time_t
53 leap second inserted at the end of June, 1993.
[all …]
|
| D | Makefile | 445 https://hpiers.obspm.fr/iers/bul/bulc/ntp/leap-seconds.list
593 LEAP_DEPS= leapseconds.awk leap-seconds.list
597 DATA= $(TDATA_TO_CHECK) backzone iso3166.tab leap-seconds.list \
623 leap-seconds.list leapseconds.awk localtime.c \
726 -f leapseconds.awk leap-seconds.list >$@.out
741 fetch-leap-seconds.list:
745 commit-leap-seconds.list: fetch-leap-seconds.list
746 author=$$($(AWK) '$(EXTRACT_AUTHOR)' leap-seconds.list) && \
747 date=$$(TZ=$(leaplist_TZ) stat -c%y leap-seconds.list) && \
749 leap-seconds.list
[all …]
|
| D | leap-seconds.list | 20 # than 0.9 second. Therefore, when necessary a "leap second" is applied to UTC.
24 # theorically possible to have a negative leap second (a second removed from UTC), but so far,
25 # all leap seconds have been positive (a second has been added to UTC). Based on what we know about
26 # the earth's rotation, it is unlikely that we will ever have a negative leap second.
30 # The first leap second was added on June 30, 1972. Until yhe year 2000, it was necessary in averag…
31 # leap second at a rate of 1 to 2 years. Since the year 2000 leap seconds are introduced with…
36 # The decision to introduce a leap second in UTC is the responsibility of the Earth Orientation Cen…
38 # Observatory. According to international agreements, leap seconds should only be scheduled for cer…
40 # and September. Since the introduction of leap seconds in 1972, only dates in June and December we…
|
| D | tzfile.5.txt | 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
[all …]
|
| D | zic.8.txt | 44 Read leap second information from the file with the given name.
45 If this option is not used, no leap second information appears
133 The output contains a truncated leap second table, which can
265 ignore leap seconds; for example, if a leap second occurs at
410 The file that describes leap seconds can have leap lines and an
419 The YEAR, MONTH, DAY, and HH:MM:SS fields tell when the leap second
422 "Stationary" if the leap second time given by the other fields should
423 be interpreted as UTC or (an abbreviation of) "Rolling" if the leap
427 Rolling leap seconds were implemented back when it was not clear
430 1... leap... Happy New Year" countdown, placing the leap second at
[all …]
|
| D | newtzset.3.txt | 35 string, UT is used, with the abbreviation "UTC" and without leap second
36 correction; please see newctime(3) for more about UT, UTC, and leap
114 years - including leap years - February
192 /usr/share/zoneinfo/GMT for UTC leap seconds
194 If /usr/share/zoneinfo/GMT is absent, UTC leap seconds are loaded from
|
| D | newctime.3.txt | 59 that timestamps must be nonnegative and must ignore leap seconds. Many
63 support leap seconds, in contradiction to POSIX.
150 /usr/share/zoneinfo/GMT for UTC leap seconds
152 If /usr/share/zoneinfo/GMT is absent, UTC leap seconds are loaded from
|
| D | NEWS | 59 The leap-seconds.list file is now copied from the IERS instead of
275 leapseconds.awk can now process a leap seconds file that never
276 expires; this might be useful if leap seconds are discontinued.
286 Note that leap seconds are planned to be discontinued by 2035.
410 as GMT is needed for leap second support whereas Etc/GMT is not.
789 zic fixes for truncation and leap second table expiration.
885 the leap second table expired, which led to far less accurate
887 cannot be converted accurately in the presence of leap seconds, it
893 outputs the expiration by appending a no-change entry to the leap
905 that omits leap second information for the range LO..B when LO
[all …]
|
| D | date.1.txt | 103 /usr/share/zoneinfo/GMT for UTC leap seconds
105 If /usr/share/zoneinfo/GMT is absent, UTC leap seconds are loaded from
|
| D | calendars | 54 those unsightly calendar gaps :-), they simply decreed that the next leap
59 they did, after all, have a leap year that year. And one in 1708. In 1712
|
| /third_party/musl/src/time/ |
| D | __secs_to_tm.c | 17 int wday, yday, leap; in __secs_to_tm() local
54 leap = !remyears && (q_cycles || !c_cycles); in __secs_to_tm()
55 yday = remdays + 31 + 28 + leap; in __secs_to_tm()
56 if (yday >= 365+leap) yday -= 365+leap; in __secs_to_tm()
|
| /third_party/musl/porting/uniproton/kernel/src/time/ |
| D | __secs_to_tm.c | 17 int wday, yday, leap; in __secs_to_tm() local
54 leap = !remyears && (q_cycles || !c_cycles); in __secs_to_tm()
55 yday = remdays + 31 + 28 + leap; in __secs_to_tm()
56 if (yday >= 365+leap) yday -= 365+leap; in __secs_to_tm()
|
| /third_party/musl/porting/liteos_a/kernel/src/time/ |
| D | __secs_to_tm.c | 17 int wday, yday, leap; in __secs_to_tm() local
54 leap = !remyears && (q_cycles || !c_cycles); in __secs_to_tm()
55 yday = remdays + 31 + 28 + leap; in __secs_to_tm()
56 if (yday >= 365+leap) yday -= 365+leap; in __secs_to_tm()
|
| /third_party/musl/porting/liteos_m/kernel/src/time/ |
| D | __secs_to_tm.c | 17 int wday, yday, leap; in __secs_to_tm() local
54 leap = !remyears && (q_cycles || !c_cycles); in __secs_to_tm()
55 yday = remdays + 31 + 28 + leap; in __secs_to_tm()
56 if (yday >= 365+leap) yday -= 365+leap; in __secs_to_tm()
|
| /third_party/libwebsockets/lib/roles/ws/ext/ |
| D | extension.c | 49 enum lws_ext_option_parser_states leap = LEAPS_SEEK_NAME; in lws_ext_parse_options() local
59 lwsl_wsi_ext(wsi, "'%c' %d", *in, leap); in lws_ext_parse_options()
60 switch (leap) { in lws_ext_parse_options()
69 leap = LEAPS_EAT_NAME; in lws_ext_parse_options()
93 leap = LEAPS_SEEK_VAL; in lws_ext_parse_options()
121 leap = LEAPS_SEEK_NAME; in lws_ext_parse_options()
130 leap = LEAPS_EAT_DEC; in lws_ext_parse_options()
151 leap = LEAPS_SEEK_ARG_TERM; in lws_ext_parse_options()
172 leap = LEAPS_SEEK_NAME; in lws_ext_parse_options()
|
| /third_party/icu/icu4c/source/test/testdata/ |
| D | calendar.txt | 237 { // month=3 is a leap month
244 { // month=3 is a leap month
251 { // month=3 is a leap month
258 { // month=3 is a leap month
316 { // month=3 is a leap month
323 { // month=3 is a leap month
330 { // month=3 is a leap month
337 { // month=3 is a leap month
344 { // month=3 is a leap month
351 { // month=3 is a leap month
[all …]
|
| /third_party/ltp/testcases/kernel/syscalls/clock_gettime/ |
| D | leapsec01.c | 125 struct timespec now, leap, start; in run_leapsec() local
137 leap = now; in run_leapsec()
138 tst_res(TINFO, "scheduling leap second %s", strtime(&leap)); in run_leapsec()
154 while (tx.time.tv_sec < leap.tv_sec + SECONDS_AFTER_LEAP) { in run_leapsec()
166 start.tv_sec += now.tv_sec - (leap.tv_sec - SECONDS_BEFORE_LEAP); in run_leapsec()
|
| /third_party/protobuf/src/google/protobuf/stubs/ |
| D | time.cc | 62 int64 SecondsPerMonth(int month, bool leap) { in SecondsPerMonth() argument
63 if (month == 2 && leap) { in SecondsPerMonth()
235 bool leap = IsLeapYear(year); in SecondsToDateTime() local
237 while (seconds >= SecondsPerMonth(month, leap)) { in SecondsToDateTime()
238 seconds -= SecondsPerMonth(month, leap); in SecondsToDateTime()
|
| /third_party/icu/icu4j/main/classes/core/src/com/ibm/icu/text/ |
| D | ChineseDateFormatSymbols.java | 99 public String getLeapMonth(int leap) { in getLeapMonth() argument
100 return isLeapMonth[leap]; in getLeapMonth()
|
| /third_party/icu/ohos_icu4j/src/main/java/ohos/global/icu/text/ |
| D | ChineseDateFormatSymbols.java | 101 public String getLeapMonth(int leap) { in getLeapMonth() argument
102 return isLeapMonth[leap]; in getLeapMonth()
|
| /third_party/icu/icu4c/source/data/locales/ |
| D | ff_Adlm.txt | 1012 leap{"{0}������"}
1015 leap{"{0}��"}
1018 leap{"{0}������"}
1023 leap{"{0}������"}
1028 leap{"{0}������"}
1031 leap{"{0}��"}
1034 leap{"{0}������"}
|
| /third_party/rust/crates/humantime/src/ |
| D | date.rs | 135 let leap = is_leap_year(year); in parse_rfc3339_weak() localVariable
138 2 if leap => (31, 29), in parse_rfc3339_weak()
156 if leap && month > 2 { in parse_rfc3339_weak()
|
| /third_party/curl/tests/data/ |
| D | test329 | 47 # using one of the 'right' zones that take into account leap seconds
|
| /third_party/skia/third_party/externals/icu/source/data/locales/ |
| D | ko.txt | 516 leap{"윤{0}"}
521 leap{"윤{0}"}
526 leap{"윤{0}"}
870 leap{"윤{0}"}
875 leap{"윤{0}"}
880 leap{"윤{0}"}
|