]> Cypherpunks repositories - gostls13.git/commit
[release-branch.go1] runtime: detect hash map collision problems
authorRuss Cox <rsc@golang.org>
Fri, 21 Sep 2012 19:53:47 +0000 (05:53 +1000)
committerRuss Cox <rsc@golang.org>
Fri, 21 Sep 2012 19:53:47 +0000 (05:53 +1000)
commit3b81bac147743fe83c7058a2394098ffd5093155
tree09b9719c7ebd1ef3bb1adc214affc353c61fbd26
parentfd70e5dd66b801abcaec16f9667d3663cb27b2d7
[release-branch.go1] runtime: detect hash map collision problems

««« backport f99b9475b914
runtime: detect hash map collision problems

This can only happen if the hash function we're using is getting
far more than it's fair share of collisions, but that has happened
to us repeatedly as we've expanded the allowed use cases for
hash tables (issue 1544, issue 2609, issue 2630, issue 2883, issue 3695).
Maybe this will help the next time we try something new.

R=golang-dev, r
CC=golang-dev
https://golang.org/cl/6306083

»»»
src/pkg/runtime/hashmap.c