aboutsummaryrefslogtreecommitdiff
path: root/src/cmd/compile/internal/ssa/magic.go
diff options
context:
space:
mode:
authorTobias Klauser <tklauser@distanz.ch>2018-11-22 11:46:44 +0100
committerTobias Klauser <tobias.klauser@gmail.com>2018-12-02 15:12:26 +0000
commit9e277f7d554455e16ba3762541c53e9bfc1d8188 (patch)
treea72e026004116edc63d3171d5d4e612ad299c265 /src/cmd/compile/internal/ssa/magic.go
parentb397248168fcb26400ac6afb88bf6080497a819e (diff)
downloadgo-9e277f7d554455e16ba3762541c53e9bfc1d8188.tar.gz
go-9e277f7d554455e16ba3762541c53e9bfc1d8188.zip
all: use "reports whether" consistently instead of "returns whether"
Follow-up for CL 147037 and after Brad noticed the "returns whether" pattern during the review of CL 150621. Go documentation style for boolean funcs is to say: // Foo reports whether ... func Foo() bool (rather than "returns whether") Created with: $ perl -i -npe 's/returns whether/reports whether/' $(git grep -l "returns whether" | grep -v vendor) Change-Id: I15fe9ff99180ad97750cd05a10eceafdb12dc0b4 Reviewed-on: https://go-review.googlesource.com/c/150918 Run-TryBot: Tobias Klauser <tobias.klauser@gmail.com> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
Diffstat (limited to 'src/cmd/compile/internal/ssa/magic.go')
-rw-r--r--src/cmd/compile/internal/ssa/magic.go2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/cmd/compile/internal/ssa/magic.go b/src/cmd/compile/internal/ssa/magic.go
index 0457e90b53..12044111ea 100644
--- a/src/cmd/compile/internal/ssa/magic.go
+++ b/src/cmd/compile/internal/ssa/magic.go
@@ -83,7 +83,7 @@ import "math/big"
// a+b has n+1 bits in it. Nevertheless, can be done
// in 2 instructions on x86.)
-// umagicOK returns whether we should strength reduce a n-bit divide by c.
+// umagicOK reports whether we should strength reduce a n-bit divide by c.
func umagicOK(n uint, c int64) bool {
// Convert from ConstX auxint values to the real uint64 constant they represent.
d := uint64(c) << (64 - n) >> (64 - n)