-
Than McIntosh authored
In the CPU profile tests for gccgo, check to make sure that the runtime's sigprof handler itself doesn't appear in the profile. Add a "skip if gccgo" guard to one testpoint. Updates #26595 Change-Id: I92a44161d61f17b9305ce09532134edd229745a7 Reviewed-on: https://go-review.googlesource.com/126316 Run-TryBot: Than McIntosh <thanm@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by:
Ian Lance Taylor <iant@golang.org>
88206b89
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| internal/profile | ||
| testdata | ||
| elf.go | ||
| label.go | ||
| label_test.go | ||
| map.go | ||
| mprof_test.go | ||
| pprof.go | ||
| pprof_test.go | ||
| proto.go | ||
| proto_test.go | ||
| protobuf.go | ||
| protomem.go | ||
| protomem_test.go | ||
| runtime.go | ||
| runtime_test.go |