diff options
| author | Russ Cox <rsc@golang.org> | 2015-05-02 22:59:35 -0400 |
|---|---|---|
| committer | Russ Cox <rsc@golang.org> | 2015-05-11 14:40:27 +0000 |
| commit | 7d9e16abc6bea2eb12d718b578f91328af99586a (patch) | |
| tree | f533b106b64b3b8428492a9a917e5befa86927a2 /src/runtime/atomic_pointer.go | |
| parent | db6f88a84b126877bd523df8c45af06779ce0e42 (diff) | |
| download | go-7d9e16abc6bea2eb12d718b578f91328af99586a.tar.xz | |
runtime: add benchmark of heapBitsSetType
There was an old benchmark that measured this indirectly
via allocation, but I don't understand how to factor out the
allocation cost when interpreting the numbers.
Replace with a benchmark that only calls heapBitsSetType,
that does not allocate. This was not possible when the
benchmark was first written, because heapBitsSetType had
not been factored out of mallocgc.
Change-Id: I30f0f02362efab3465a50769398be859832e6640
Reviewed-on: https://go-review.googlesource.com/9701
Reviewed-by: Austin Clements <austin@google.com>
Diffstat (limited to 'src/runtime/atomic_pointer.go')
0 files changed, 0 insertions, 0 deletions
