Since I read it in #1 and nowhere else, I want to clarify this: the throughput numbers in benchmark/throughput/*.csv, are they the computed average as the timing-harness prints (i.e., (measuremnt(200it) - measurement(100it)) / 100) or are they something else?
For example:
# hex encoded block: 81fdffff0000
.section __TEXT,__text,regular,pure_instructions
cmpl $65535, %ebp ## imm = 0xFFFF
# bhive measured throughput: 33.000000
does this say that cmpl immediate, gpr64 has been measured with a derived (reciprocal) throughput of 0.33cy (i.e. 3 instruction per cycle) or 33cy?
Maybe this could be mentioned in the README.md :)
Since I read it in #1 and nowhere else, I want to clarify this: the throughput numbers in
benchmark/throughput/*.csv, are they the computed average as the timing-harness prints (i.e.,(measuremnt(200it) - measurement(100it)) / 100) or are they something else?For example:
does this say that
cmpl immediate, gpr64has been measured with a derived (reciprocal) throughput of 0.33cy (i.e. 3 instruction per cycle) or 33cy?Maybe this could be mentioned in the README.md :)