runtime: unsafe pointer maps

[RLH]

There are several places in the code where pointers are stored into slots that the pointer maps do not note as holding pointers.

While the occurrences found so far appear benign with the current GC they do prevent adding diagnostics to the write barrier intended to detect errant writes. At the very least they should be documented as to why they are benign.

[robpike]

It would be nice to list those locations here.

[RLH]

Here is the work in progress CL for the ones I've found so far. https://go-review.googlesource.com/c/go/+/80975

…

On Wed, Nov 29, 2017 at 9:54 PM, Rob Pike ***@***.***> wrote: It would be nice to list those locations here. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#22931 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA7Wn8TjMg1dI72aCasQ37h20JL0yQngks5s7hjmgaJpZM4Qvoq4> .

[odeke-em]

Great, thank you @RLH for the report and for the initial CL to get things rolling!

I am going to also kindly page @josharian @randall77 @mknyszek @aclements who might
all be interested in this issue and then punt this issue to Go1.13.