runtime: malloc flags should be subsumed by the type information provided to mallogc

[lexprfuncall]

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
values.

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.

[rsc]

Comment 1:

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

[rsc]

Comment 2:

Labels changed: added repo-main.

[martisch]

Current runtime malloc takes a type and derives the pointer or no-pointer properties from the type.

go/src/runtime/malloc.go

Line 903 in d83168e

func mallocgc(size uintptr, typ *_type, needzero bool) unsafe.Pointer {

This issue seems to have therefore been adressed sometime in the last 5+ years and can be closed.