So, hash has been on my mind lately. No, not that kind of hash, or that kind either. First, there was last week, when I installed Internet Explorer 8 beta 1. I was reading the release notes and was amazed to find that # (you know, octothorpe, pound sign) was not considered part of the URL by this version. Thus you can't link directly to a named element on a page. Eeew!
Then today, Hugh Brown dropped a comment on my diatribe post about value-types, reference-types, Equals and GetHashCode. The post has been live for many months now, and has quite a bit of Google juice. Until now, nobody has ever quibbled with the stuff I wrote, but Hugh had some interesting observations.
First the little stuff
In a minor part of his comment, he was surprised by the many overloads of GetHashCode that I suggest, wondering why I didn't just always expect callers to use the params int[] version. Quite simply, this is because by providing several overloads for a small number of arguments (5 in my example), I avoid paying the cost of allocating the array of integers and copying the values for each call to the CombineHashCodes. While this may seem like a trivial savings, remember that GetHashCode is called many times when dealing with HashTable collections and thus it is worth it to provide expedited code paths for the more common usages. Additional savings inside the CombineHashCodes method are garnered by avoiding the loop setup/iteration overhead. Finally, in optimized builds, these simpler method calls will be inlined by the compiler and/or JIT, where methods having loops in the body are never inlined (in CLR releases thus far). It is worth noting that the .Net runtime implementation does the same thing for System.Web.Util.HashCodeCombiner and System.String.Format.
To the meat of the comment
The main body of his comment was that my code actually didn't return useful values. That concerned me a lot. Given his use of Python and inlined implementation, I had to write my own test jig. Unfortunately it confirmed his complaint. On the one hand, the values he was using to test were not normal values you would expect from GetHashCode. Normally GetHashCode values are well-distributed across the entire 32-bit range of an Int32. He was using sequential, smallish, numbers which was skewing the result oddly. That said, the values SHOULD have been different for very-similar inputs. I delved a little into the code I originally wrote and found that what's on the web page does NOT match what is now in use in the BCL's internal code to combine hash codes (which is where I got the idea of left-shifting by 5 bits before XORing). I think that my code was originally based on the 1.1 BCL but I'm not really sure.
In the .Net 2.0 version, there's a class called System.Web.Util.HashCodeCombiner that actually reflects essentially the same technique as my code, with one huge and very significant difference. Where I simply left-shift the running hash code by 5 bits and then XOR in the next value, they are doing the left-shift and also adding in the running hash, then doing the XOR.
Why so shifty, anyway?
You might be wondering why do the left shift in the first place. The simple answer is that by doing a left-shift by some number of bits, we preserve the low order bits of the running hash somewhat. This prevents the incoming value from XORing away all the significance of the bits thus far, and also insures that low-byte-only intermediate hash codes don't simply cancel each other out. By shifting left 5 digits, we're simply multiplying by 32 (and thus preserving the lowest 5 digits). Then the original running hash value is added in on more time, making the effective multiplier 33. This isn't far off from Hugh's suggestion of multiplying by 37, while being significantly faster in the binary world of computers. Once the shift and add (e.g. multiplication by 33) is completed, the XOR of the new values results in much better distribution of the final value.
I've updated my code in the Utilities library, and I'm going back to the original post to point to this post and the new code. So, I owe you one, Hugh...and maybe Microsoft does too because while I was reviewing their code in the newly released BCL source code, I found a very unexpected implementation. This is the snippet in question:
internal static int CombineHashCodes(int h1, int h2) {
return ((h1 << 5) + h1) ^ h2;
}
internal static int CombineHashCodes(int h1, int h2, int h3) {
return CombineHashCodes(CombineHashCodes(h1, h2), h3);
}
internal static int CombineHashCodes(int h1, int h2, int h3, int h4) {
return CombineHashCodes(CombineHashCodes(h1, h2), CombineHashCodes(h3, h4));
}
internal static int CombineHashCodes(int h1, int h2, int h3, int h4, int h5) {
return CombineHashCodes(CombineHashCodes(h1, h2, h3, h4), h5);
}Did you see the oddity? That implementation taking 4 values does its work by calling the two-value one three times. Once to combine the first pair (h1 and h2) of arguments, once to combine the second pair (h3 and h4), then finally to combine the two intermediate values. That's a bit different than doing what the 3-value and 5-value overloads use. I personally think it should have called the 2-value against output of the 3-value to combine the 4th value (h4). That would be more like what the 3-value and 5-value overload do. In other words, the method should be:
internal static int CombineHashCodes(int h1, int h2, int h3, int h4) {
return CombineHashCodes(CombineHashCodes(h1, h2, h3), h4);
}
Perhaps they don't care that the values are inconsistent, especially since they don't provide a combiner that takes a params int[] overload, but imagine if I had blindly copied that code and you got two different values from this:
Console.WriteLine("Testing gotcha:");
Console.WriteLine(String.Format("1,2: {0:x}", Utilities.CombineHashCodes(1, 2)));
Console.WriteLine(String.Format("1,2,3: {0:x}", Utilities.CombineHashCodes(1, 2, 3)));
Console.WriteLine(String.Format("1,2,3,4: {0:x}", Utilities.CombineHashCodes(1, 2, 3, 4)));
Console.WriteLine(String.Format("1,2,3,4,5: {0:x}", Utilities.CombineHashCodes(1, 2, 3, 4, 5)));
Console.WriteLine(String.Format("[1,2]: {0:x}", Utilities.CombineHashCodes(new int[] { 1, 2 })));
Console.WriteLine(String.Format("[1,2,3]: {0:x}", Utilities.CombineHashCodes(new int[] { 1, 2, 3 })));
Console.WriteLine(String.Format("[1,2,3,4]: {0:x}", Utilities.CombineHashCodes(new int[] { 1, 2, 3, 4 })));
Console.WriteLine(String.Format("[1,2,3,4,5]: {0:x}", Utilities.CombineHashCodes(new int[] { 1, 2, 3, 4, 5 })));
Where we are at now
Here is the revised version of the CombineHashCodes methods from my Utilities library
public static partial class Utilities
{
public static int CombineHashCodes(params int[] hashes)
{
int hash = 0;
for (int index = 0; index < hashes.Length; index++)
{
hash = (hash << 5) + hash;
hash ^= hashes[index];
}
return hash;
}
private static int GetEntryHash(object entry)
{
int entryHash = 0x61E04917; // slurped from .Net runtime internals...
if (entry != null)
{
object[] subObjects = entry as object[];
if (subObjects != null)
{
entryHash = Utilities.CombineHashCodes(subObjects);
}
else
{
entryHash = entry.GetHashCode();
}
}
return entryHash;
}
public static int CombineHashCodes(params object[] objects)
{
int hash = 0;
for (int index = 0; index < objects.Length; index++)
{
hash = (hash << 5) + hash;
hash ^= GetEntryHash(objects[index]);
}
return hash;
}
public static int CombineHashCodes(int hash1, int hash2)
{
return ((hash1 << 5) + hash1)
^ hash2;
}
public static int CombineHashCodes(int hash1, int hash2, int hash3)
{
int hash = CombineHashCodes(hash1, hash2);
return ((hash << 5) + hash)
^ hash3;
}
public static int CombineHashCodes(int hash1, int hash2, int hash3, int hash4)
{
int hash = CombineHashCodes(hash1, hash2, hash3);
return ((hash << 5) + hash)
^ hash4;
}
public static int CombineHashCodes(int hash1, int hash2, int hash3, int hash4, int hash5)
{
int hash = CombineHashCodes(hash1, hash2, hash3, hash4);
return ((hash << 5) + hash)
^ hash5;
}
public static int CombineHashCodes(object obj1, object obj2)
{
return CombineHashCodes(obj1.GetHashCode()
, obj2.GetHashCode());
}
public static int CombineHashCodes(object obj1, object obj2, object obj3)
{
return CombineHashCodes(obj1.GetHashCode()
, obj2.GetHashCode()
, obj3.GetHashCode());
}
public static int CombineHashCodes(object obj1, object obj2, object obj3, object obj4)
{
return CombineHashCodes(obj1.GetHashCode()
, obj2.GetHashCode()
, obj3.GetHashCode()
, obj4.GetHashCode());
}
public static int CombineHashCodes(object obj1, object obj2, object obj3, object obj4, object obj5)
{
return CombineHashCodes(obj1.GetHashCode()
, obj2.GetHashCode()
, obj3.GetHashCode()
, obj4.GetHashCode()
, obj5.GetHashCode());
}
}
Posts
