Revert "runtime: diagnose invalid pointers during GC"

Broke arm64. Update #9880.

This reverts commit 38d9b2a3a942892193195a6912ab23cdaff23e20.

Change-Id: I35fa21005af2183828a9d8b195ebcfbe45ec5138
Reviewed-on: https://go-review.googlesource.com/12247
Reviewed-by: Russ Cox <rsc@golang.org>

diff --git a/src/runtime/mbitmap.go b/src/runtime/mbitmap.go
index b9b52a7bc416f8974a465534a9b9fa2579d0033c..ef17409ebeb73cc57a4161eacae415cd462853f2 100644 (file)
--- a/src/runtime/mbitmap.go
+++ b/src/runtime/mbitmap.go
@@ -201,7 +201,7 @@ func heapBitsForObject(p uintptr) (base uintptr, hbits heapBits, s *mspan) {
                // The following ensures that we are rigorous about what data
                // structures hold valid pointers.
                // TODO(rsc): Check if this still happens.
-               if true {
+               if false {
                        // Still happens sometimes. We don't know why.
                        printlock()
                        print("runtime:objectstart Span weird: p=", hex(p), " k=", hex(k))