diff options
| author | h_east <h.east.727@gmail.com> | 2023-10-03 04:47:13 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-10-02 21:47:13 +0200 |
| commit | ba77bbb5c775663a8b55871f753d7b1b570bb9ba (patch) | |
| tree | 323ec37bead65ca92fb42fc376b2e07b41a23efb /runtime/doc/repeat.txt | |
| parent | b32064fedbeb689ecb0481e9473cb7b87d5bb805 (diff) | |
runtime(doc): fix typos.
* Fix typo in document (Related: #12516)
* Fix E1363 duplication
* Fix one more typo.
Signed-off-by: Christian Brabandt <cb@256bit.org>
Diffstat (limited to 'runtime/doc/repeat.txt')
| -rw-r--r-- | runtime/doc/repeat.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/runtime/doc/repeat.txt b/runtime/doc/repeat.txt index 17dffa82f7..247dd0992c 100644 --- a/runtime/doc/repeat.txt +++ b/runtime/doc/repeat.txt @@ -1149,8 +1149,8 @@ Profiling should give a good indication of where time is spent, but keep in mind there are various things that may clobber the results: - The accuracy of the time measured depends on the gettimeofday(), or - clock_gettime if available, system function. The accuracy ranges from 1/100 - second to nanoseconds. With clock_gettime the times are displayed in + clock_gettime() if available, system function. The accuracy ranges from + 1/100 second to nanoseconds. With clock_gettime() the times are displayed in nanoseconds, otherwise microseconds. You can use `has("prof_nsec")`. - Real elapsed time is measured, if other processes are busy they may cause |