Change https://golang.org/cl/138586 mentions this issue: [release-branch.go1.10] reflect: fix s390x reflect method calls

Change https://golang.org/cl/138585 mentions this issue: [release-branch.go1.10] reflect: ensure correct scanning of return values

Change https://golang.org/cl/138584 mentions this issue: [release-branch.go1.10] reflect: use correct write barrier operations for method funcs

Change https://golang.org/cl/138587 mentions this issue: [release-branch.go1.10] runtime: don't dereference 0-length bitvectors

@randall77 This patch does not apply cleanly to release-branch.go1.10 right now. If you still think this should be backported, can you please make a cherry-pick CL as described at https://golang.org/wiki/MinorReleases#making-cherry-pick-cls?

We can also decide this doesn't meet the backport policy criteria, since there is a workaround (update to Go 1.11.1, where this issue is resolved).

Edit: I'll move the milestone to Go 1.10.6 since it's too late for Go 1.10.5 release that's happening today.

Change https://golang.org/cl/147237 mentions this issue: [release-branch.go1.10] reflect: ensure correct scanning of return values

@randall77, given the fix in 1.11 and the proximity to 1.12, is this still worth backporting to 1.10?

This fix is backported to 1.11, and then upgrading to 1.11 will be a valid workaround, so this is not eligible for backport to 1.10.