Commit 6afb5fa4 authored by Austin Clements's avatar Austin Clements

runtime: remove GoSched/GoStart trace events around GC

These were appropriate for STW GC, since it interrupted the allocating
Goroutine, but don't apply to concurrent GC, which runs on its own
Goroutine. Forced GC is still STW, but it makes sense to attribute the
GC to the goroutine that called runtime.GC().

Change-Id: If12418ca66dc7e53b8b16025af4e03adb5d9577e
Reviewed-on: https://go-review.googlesource.com/8715Reviewed-by: default avatarDmitry Vyukov <dvyukov@google.com>
Reviewed-by: default avatarRick Hudson <rlh@golang.org>
parent eec6fdc9
......@@ -324,7 +324,6 @@ func gc(mode int) {
}
if trace.enabled {
traceGoSched()
traceGCStart()
}
......@@ -459,7 +458,6 @@ func gc(mode int) {
if trace.enabled {
traceGCDone()
traceGoStart()
}
// all done
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment