@@ -68,7 +68,7 @@ and likely more unpublished programs.
68
68
69
69
### Benchmark runners
70
70
71
- Multiple tools have also been written that process this format.
71
+ Multiple tools have also been written that generate this format.
72
72
In addition to the standard Go testing package,
73
73
[ compilebench] ( https://godoc.org/rsc.io/compilebench )
74
74
generates this data format based on runs of the Go compiler,
@@ -93,7 +93,7 @@ have semantic meaning in the reporting of benchmark results.
93
93
All other lines in the data file, including but not limited to
94
94
blank lines and lines beginning with a # character, are ignored.
95
95
For example, the testing package prints test results above benchmark data,
96
- usually the text ` PASS ` . that line is neither a configuration line nor a benchmark
96
+ usually the text ` PASS ` . That line is neither a configuration line nor a benchmark
97
97
result line, so it is ignored.
98
98
99
99
### Configuration Lines
@@ -106,6 +106,7 @@ where key contains no space characters (as defined by `unicode.IsSpace`)
106
106
nor upper case characters (as defined by ` unicode.IsUpper ` ),
107
107
and space characters separate “key:” from “value.”
108
108
Conventionally, multiword keys are written with the words
109
+ separated by hyphens, as in cpu-speed.
109
110
There are no restrictions on value, except that it cannot contain a newline character.
110
111
Value can be omitted entirely but the colon must still be present.
111
112
0 commit comments