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.
This commit is contained in:
parent
27cbcd6241
commit
a6be61ec71
|
@ -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;
|
||||
|
|
Loading…
Reference in New Issue