From: Gregory P. Smith <greg@krypto.org>
Date: Tue, 11 Dec 2012 02:34:09 +0000 (-0800)
Subject: Keep y a Py_hash_t instead of Py_uhash_t as it is compared with == -1 and the
X-Git-Tag: v3.3.1rc1~538^2
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=a6be61ec71be600e1d270aea17f1d90dccf6088b;p=python

Keep y a Py_hash_t instead of Py_uhash_t as it is compared with == -1 and the
compiler logic will do the right thing with just x as a Py_uhash_t.  This
matches what was already done in the 3.3 version.

cleanup only - no functionality or hash values change.
---

diff --git a/Objects/tupleobject.c b/Objects/tupleobject.c
index c725227979..9e914cb634 100644
--- a/Objects/tupleobject.c
+++ b/Objects/tupleobject.c
@@ -315,7 +315,8 @@ error:
 static Py_hash_t
 tuplehash(PyTupleObject *v)
 {
-    register Py_uhash_t x, y;  /* Unsigned for defined overflow behavior. */
+    register Py_uhash_t x;  /* Unsigned for defined overflow behavior. */
+    register Py_hash_t y;
     register Py_ssize_t len = Py_SIZE(v);
     register PyObject **p;
     Py_uhash_t mult = _PyHASH_MULTIPLIER;