Home
last modified time | relevance | path

Searched refs:nanosecond (Results 1 – 25 of 142) sorted by relevance

123456

/external/autotest/client/site_tests/platform_HighResTimers/
Dcontrol8 CRITERIA = "Fails if no timers have nanosecond resolution."
17 Reads from /proc/timer_list to see if any reported timers have nanosecond
/external/autotest/site_utils/
Dcloud_console.proto23 // nanosecond resolution.
27 // Non-negative fractions of a second at nanosecond resolution.
/external/libcxx/docs/DesignDocs/
DFileTimeType.rst36 nanosecond resolution, and (B) use more than 64 bits (assuming a 64 bit ``time_t``).
57 To get nanosecond resolution, we simply define ``period`` to be ``std::nano``.
76 at nanosecond resolution.
80 and with nanosecond resolution).
141 So we might ask: Do users "need" nanosecond precision? Is seconds not good enough?
280 a nanosecond tick period; which is the only case where the names ``tv_sec``
283 When we convert a nanosecond duration to seconds, ``fs_timespec_rep`` will
398 * Its the representation used by chrono's ``nanosecond`` and ``second`` typedefs.
447 a nanosecond tick period.
452 * It has a larger range when representing any period longer than a nanosecond.
[all …]
/external/icu/icu4c/source/data/unit/
Dce.txt51 nanosecond{
203 nanosecond{
Dsmn.txt28 nanosecond{
Dsah.txt102 nanosecond{
385 nanosecond{
Dzh_Hant_HK.txt108 nanosecond{
400 nanosecond{
647 nanosecond{
Dbs_Cyrl.txt114 nanosecond{
Dmzn.txt146 nanosecond{
656 nanosecond{
Dzh.txt232 nanosecond{
884 nanosecond{
1404 nanosecond{
Dceb.txt282 nanosecond{
283 dnam{"mga nanosecond"}
284 one{"{0} ka nanosecond"}
285 other{"{0} ka mga nanosecond"}
1187 nanosecond{
Dyue.txt235 nanosecond{
901 nanosecond{
1428 nanosecond{
Dyue_Hans.txt236 nanosecond{
902 nanosecond{
1429 nanosecond{
Dml.txt282 nanosecond{
983 nanosecond{
1540 nanosecond{
Dfr_CA.txt169 nanosecond{
552 nanosecond{
835 nanosecond{
Dfa.txt281 nanosecond{
1034 nanosecond{
1570 nanosecond{
Dzh_Hant.txt232 nanosecond{
935 nanosecond{
1570 nanosecond{
Dko.txt227 nanosecond{
804 nanosecond{
1264 nanosecond{
Dja.txt236 nanosecond{
904 nanosecond{
1477 nanosecond{
Dbn.txt273 nanosecond{
1004 nanosecond{
1559 nanosecond{
/external/protobuf/src/google/protobuf/
Dduration.proto44 // as a count of seconds and fractions of seconds at nanosecond
98 // encoded in JSON format as "3s", while 3 seconds and 1 nanosecond should
109 // Signed fractions of a second at nanosecond resolution of the span
Dtimestamp.proto45 // nanosecond resolution. The count is relative to an epoch at UTC midnight on
106 // seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution),
133 // Non-negative fractions of a second at nanosecond resolution. Negative
/external/golang-protobuf/ptypes/duration/
Dduration.proto44 // as a count of seconds and fractions of seconds at nanosecond
98 // encoded in JSON format as "3s", while 3 seconds and 1 nanosecond should
110 // Signed fractions of a second at nanosecond resolution of the span
/external/golang-protobuf/ptypes/timestamp/
Dtimestamp.proto45 // nanosecond resolution in UTC Epoch time. It is encoded using the
104 // seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution),
130 // Non-negative fractions of a second at nanosecond resolution. Negative
/external/u-boot/include/
Defi.h230 u32 nanosecond; member

123456