| /openbsd/src/gnu/usr.bin/perl/ |
| D | time64.c | 323 int leap; in Perl_gmtime64_r() local
404 leap = IS_LEAP (year); in Perl_gmtime64_r()
405 while (m >= (Time64_T) length_of_year[leap]) { in Perl_gmtime64_r()
406 m -= (Time64_T) length_of_year[leap]; in Perl_gmtime64_r()
408 leap = IS_LEAP (year); in Perl_gmtime64_r()
413 while (m >= (Time64_T) days_in_month[leap][v_tm_mon]) { in Perl_gmtime64_r()
414 m -= (Time64_T) days_in_month[leap][v_tm_mon]; in Perl_gmtime64_r()
430 leap = IS_LEAP (year); in Perl_gmtime64_r()
431 while (m < (Time64_T) -length_of_year[leap]) { in Perl_gmtime64_r()
432 m += (Time64_T) length_of_year[leap]; in Perl_gmtime64_r()
[all …]
|
| /openbsd/src/share/zoneinfo/datfiles/ |
| D | leap-seconds.list | 1 # $OpenBSD: leap-seconds.list,v 1.5 2025/01/19 22:03:27 millert Exp $
21 # than 0.9 seconds. Therefore, when necessary a "leap second" is applied to UTC.
25 # theoretically possible to have a negative leap second (a second removed from UTC), but so far,
26 # all leap seconds have been positive (a second has been added to UTC). Based on what we know about
27 # the earth's rotation, it is unlikely that we will ever have a negative leap second.
31 # The first leap second was added on June 30, 1972. Until the year 2000, it was necessary in averag…
32 # leap second at a rate of 1 to 2 years. Since the year 2000 leap seconds are introduced with…
37 # The decision to introduce a leap second in UTC is the responsibility of the Earth Orientation Cen…
39 # Observatory. According to international agreements, leap seconds should be scheduled only for cer…
41 # and September. Since the introduction of leap seconds in 1972, only dates in June and December we…
|
| D | etcetera | 24 # Functions like gmtime load the "GMT" file to handle leap seconds properly.
|
| D | northamerica | 3470 # The alterpresse.org source seems to show a US-style leap from 2:00 a.m. to
|
| /openbsd/src/usr.bin/cal/ |
| D | README | 13 add the number of leap years (days?) since year 1
16 this compensates for the non-inclusive leap year
31 It must be noted that the number of leap years calculation is sensitive
32 to the date for which the leap year is being calculated. A year that occurs
33 before the reformation is determined to be a leap year if its modulo of
34 4 equals zero. But after the reformation, a year is only a leap year if
37 zero, then the year is a leap year anyway. This is, in fact, what the
|
| D | cal.c | 447 int i, leap; in day_in_year() local
449 leap = leap_year(year); in day_in_year()
451 day += days_in_month[leap][i]; in day_in_year()
|
| /openbsd/src/usr.bin/file/magdir/ |
| D | timezone | 18 >28 belong 0 \b, no leap seconds
19 >28 belong 1 \b, 1 leap second
20 >28 belong >1 \b, %d leap seconds
|
| /openbsd/src/share/zoneinfo/ |
| D | Makefile | 110 leapseconds: leapseconds.awk datfiles/leap-seconds.list
112 ${.CURDIR}/datfiles/leap-seconds.list >${.OBJDIR}/$@.out
144 ${INSTALL} -c -o root -g bin -m 644 ${.CURDIR}/datfiles/leap-seconds.list \
|
| /openbsd/src/sys/dev/fdt/ |
| D | acrtc.c | 200 uint16_t leap = isleap(dt->dt_year) ? RTC_YEA_LEAP_YEAR : 0; in acrtc_clock_write() local
208 acrtc_write_reg(sc, RTC_YEA, TOBCD(dt->dt_year - 2000) | leap); in acrtc_clock_write()
|
| /openbsd/src/lib/libc/time/ |
| D | README | 36 Since POSIX frowns on correct leap second handling, the default behavior of
38 leap second information from its output files.
|
| D | Theory | 97 * POSIX requires that systems ignore leap seconds.
150 * These functions can account for leap seconds, thanks to Bradley White.
440 those unsightly calendar gaps :-), they simply decreed that the next leap
445 they did, after all, have a leap year that year. And one in 1708. In 1712
|
| /openbsd/src/games/quiz/datfiles/ |
| D | collectives | 49 leopards:leap
|
| /openbsd/src/gnu/usr.bin/cvs/doc/ |
| D | RCSFILES | 242 +Times use UTC, except that for portability's sake leap seconds are not allowed;
243 +implementations that support leap seconds should output
247 +during an inserted leap second, and should accept
249 +for a deleted leap second.
|
| /openbsd/src/gnu/usr.bin/perl/cpan/Time-Piece/t/ |
| D | 07arith.t | 22 # this one wraps around to March because of the leap year
|
| /openbsd/src/usr.sbin/ntpd/ |
| D | server.c | 180 reply.status = lconf->status.leap; in server_dispatch()
|
| D | ntpd.h | 143 u_int8_t leap; member
|
| D | ntp.c | 805 conf->status.leap = offsets[i]->status.leap; in priv_adjtime()
|
| D | client.c | 402 p->reply[p->shift].status.leap = (msg.status & LIMASK); in client_dispatch()
|
| /openbsd/src/gnu/usr.bin/perl/cpan/Test-Simple/lib/Test/ |
| D | Tutorial.pod | 262 Does it get leap years right? We could keep repeating the code above,
|
| /openbsd/src/share/snmp/ |
| D | SNMPv2-TC.txt | 699 (use 60 for leap-second)
|
| /openbsd/src/gnu/usr.bin/gcc/gcc/f/ |
| D | intdoc.in | 1221 Seconds after the minute, range 0--59 or 0--61 to allow for leap
1260 Seconds after the minute, range 0--59 or 0--61 to allow for leap
|
| /openbsd/src/gnu/llvm/clang/include/clang/Tooling/Inclusions/ |
| D | StdSymbolMap.inc | 1366 SYMBOL(leap, std::chrono::, <chrono>)
|
| /openbsd/src/games/fortune/datfiles/ |
| D | fortunes-o | 1525 Then leap up and snap;
|
| /openbsd/src/gnu/gcc/libcpp/po/ |
| D | el.po | 1240 #~ msgstr "repeated leap second moment"
|
| /openbsd/src/gnu/usr.bin/perl/Porting/ |
| D | epigraphs.pod | 819 There are some things one can only achieve by a deliberate leap
2947 To leap up into joy celestial.
|