1
0
mirror of https://github.com/golang/go synced 2024-11-23 00:30:07 -07:00

all: fix two minor typos in comments

Change-Id: Iec6cd81c9787d3419850aa97e75052956ad139bc
Reviewed-on: https://go-review.googlesource.com/c/go/+/221789
Reviewed-by: Emmanuel Odeke <emm.odeke@gmail.com>
This commit is contained in:
Josh Bleecher Snyder 2017-05-09 12:48:23 -07:00
parent ea1437a8cd
commit b49d8ce2fa
2 changed files with 2 additions and 2 deletions

View File

@ -326,7 +326,7 @@ func push(s *gc.SSAGenState, v *ssa.Value) {
}
// popAndSave pops a value off of the floating-point stack and stores
// it in the reigster assigned to v.
// it in the register assigned to v.
func popAndSave(s *gc.SSAGenState, v *ssa.Value) {
r := v.Reg()
if _, ok := s.SSEto387[r]; ok {

View File

@ -125,7 +125,7 @@ As a general guideline, test functions should be small, to avoid
possible interactions between unrelated lines of code that may be
introduced, for example, by the compiler's optimization passes.
Any given line of Go code could get assigned more instructions that it
Any given line of Go code could get assigned more instructions than it
may appear from reading the source. In particular, matching all MOV
instructions should be avoided; the compiler may add them for
unrelated reasons and this may render the test ineffective.