Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

runtime: unsafe pointer maps #22931

RLH opened this Issue Nov 29, 2017 · 3 comments


None yet
4 participants
Copy link

RLH commented Nov 29, 2017

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.


This comment has been minimized.

Copy link

robpike commented Nov 30, 2017

It would be nice to list those locations here.


This comment has been minimized.

Copy link
Contributor Author

RLH commented Nov 30, 2017


This comment has been minimized.

Copy link

odeke-em commented Feb 4, 2019

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.

@odeke-em odeke-em modified the milestones: Go1.12, Go1.13 Feb 4, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.