code review 7663051: runtime: optionally check all allocations in hashmap.c

runtime: optionally check all allocations in hashmap.c

Adds the new debugging constant 'checkgc'. If its value is non-zero
all calls to mallocgc() from hashmap.c will start a garbage collection.

Fixes issue 5074.

[atom, 2013-03-23 08:51:19]

Hello golang-dev@googlegroups.com (cc: rsc, khr),

I'd like you to review this change to
https://code.google.com/p/go/

[khr, 2013-03-23 15:58:16]

On 2013/03/23 08:51:19, atom wrote:
> Hello mailto:golang-dev@googlegroups.com (cc: rsc, khr),
> 
> I'd like you to review this change to
> https://code.google.com/p/go/

LGTM

[rsc, 2013-03-25 20:26:29]

(You don't need to wait for me, if you are.)

[atom, 2013-03-25 20:35:32]

On 2013/03/25 20:26:29, rsc wrote:
> (You don't need to wait for me, if you are.)

Ok. As far as I understand, the reason for reopening issue 5074 has been the
major change to hashmap.c.

[atom, 2013-03-25 20:35:55]

*** Submitted as https://code.google.com/p/go/source/detail?r=f0a9210fdd8c ***

runtime: optionally check all allocations in hashmap.c

Adds the new debugging constant 'checkgc'. If its value is non-zero
all calls to mallocgc() from hashmap.c will start a garbage collection.

Fixes issue 5074.

R=golang-dev, khr
CC=golang-dev, rsc
https://codereview.appspot.com/7663051