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: malloc flags should be subsumed by the type information provided to mallogc #6237

lexprfuncall opened this issue Aug 23, 2013 · 2 comments


Copy link

@lexprfuncall lexprfuncall commented Aug 23, 2013

Today, we pass flags to malloc to help it decide what constraints are required on the
storage allocated for an object.  However, all of this information can be derrived from
the type of an object.

For example, instead of passing the "not pointers" flag mallocgc can do a
"no pointers" allocation whenever it is passed a type which contains no point

There are some flags which cannot be subsumed by the type information, this includes the
zeroing flag (sometimes we know we are going to initialize an object and do not need
zeroing) and the no invoke gc flag.  The "no gc" flag is a gray area, in
theory types could encode this information (for example, mspans, stacks) but today those
kinds of allocation have no type.  Maybe they should.

This comment has been minimized.

Copy link

@rsc rsc commented Dec 4, 2013

Comment 1:

Labels changed: added release-none, removed go1.3maybe.


This comment has been minimized.

Copy link

@rsc rsc commented Dec 4, 2013

Comment 2:

Labels changed: added repo-main.

@rsc rsc added this to the Unplanned milestone Apr 10, 2015
@rsc rsc removed release-none labels Apr 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.