]> Cypherpunks.ru repositories - gostls13.git/commitdiff
runtime: typo fix cyle -> cycle
author“kinggo” <1510613524@qq.com>
Mon, 20 Dec 2021 05:54:27 +0000 (05:54 +0000)
committerZhuo Meng <mzh@golangcn.org>
Tue, 21 Dec 2021 01:51:23 +0000 (01:51 +0000)
Change-Id: I213fa8aa9b9c2537a189677394ddd30c62312518
GitHub-Last-Rev: ccafdee9440b06232cdfca83099bf0aeff62a4c0
GitHub-Pull-Request: golang/go#50268
Reviewed-on: https://go-review.googlesource.com/c/go/+/373336
Reviewed-by: Ian Lance Taylor <iant@golang.org>
Run-TryBot: Ian Lance Taylor <iant@golang.org>
TryBot-Result: Gopher Robot <gobot@golang.org>
Reviewed-by: Zhuo Meng <mzh@golangcn.org>
src/runtime/mgcmark.go
src/runtime/mgcsweep.go

index a15c62cc491eee2c92ad87af5f09c0892266e781..68acfd4d498fa9aa5f3737eafc449f76ab3aab37 100644 (file)
@@ -1561,7 +1561,7 @@ func gcmarknewobject(span *mspan, obj, size, scanSize uintptr) {
        if !goexperiment.PacerRedesign {
                // The old pacer counts newly allocated memory toward
                // heapScanWork because heapScan is continuously updated
-               // throughout the GC cyle with newly allocated memory. However,
+               // throughout the GC cycle with newly allocated memory. However,
                // these objects are never actually scanned, so we need
                // to account for them in heapScanWork here, "faking" their work.
                // Otherwise the pacer will think it's always behind, potentially
index fdbec30cf121d88f792e49059e98cd4f61fd521d..a46f4ec2c6cf893b5d607e34432e28d3383ac077 100644 (file)
@@ -393,7 +393,7 @@ func sweepone() uintptr {
                // The scavenger is signaled by the last sweeper because once
                // sweeping is done, we will definitely have useful work for
                // the scavenger to do, since the scavenger only runs over the
-               // heap once per GC cyle. This update is not done during sweep
+               // heap once per GC cycle. This update is not done during sweep
                // termination because in some cases there may be a long delay
                // between sweep done and sweep termination (e.g. not enough
                // allocations to trigger a GC) which would be nice to fill in