mat: work around change in cmd/compile unsigned integer behaviour
This prevents the change in golang/go@ea3bfba87c from giving us crazy
offsets when a is after b.
diff --git a/mat/offset.go b/mat/offset.go
index 830589d..3dc2e16 100644
--- a/mat/offset.go
+++ b/mat/offset.go
@@ -16,7 +16,7 @@
// This expression must be atomic with respect to GC moves.
// At this stage this is true, because the GC does not
// move. See https://golang.org/issue/12445.
- return int(uintptr(unsafe.Pointer(&b[0]))-uintptr(unsafe.Pointer(&a[0]))) / int(unsafe.Sizeof(float64(0)))
+ return (int(uintptr(unsafe.Pointer(&b[0]))) - int(uintptr(unsafe.Pointer(&a[0])))) / int(unsafe.Sizeof(float64(0)))
}
// offsetComplex returns the number of complex128 values b[0] is after a[0].
@@ -27,5 +27,5 @@
// This expression must be atomic with respect to GC moves.
// At this stage this is true, because the GC does not
// move. See https://golang.org/issue/12445.
- return int(uintptr(unsafe.Pointer(&b[0]))-uintptr(unsafe.Pointer(&a[0]))) / int(unsafe.Sizeof(complex128(0)))
+ return (int(uintptr(unsafe.Pointer(&b[0]))) - int(uintptr(unsafe.Pointer(&a[0])))) / int(unsafe.Sizeof(complex128(0)))
}
