Fix 32-bit versus 64-bit boolean_function issue in crypto

[kcrisman]

See #6870 for some discussion. A random test behaves differently in 32/64 cases:

sage -t -long devel/sage/sage/crypto/boolean_function.pyx
**********************************************************************
File "/scratch/mvngu/release/sage-4.1.2.alpha2/devel/sage-main/sage/crypto/boolean_function.pyx", line 1013:
    sage: B.nonlinearity()
Expected:
    217
Got:
    222
**********************************************************************
1 items had failures:
   1 of   6 in __main__.example_36
***Test Failed*** 1 failures.
For whitespace errors, see the file /home/mvngu/.sage//tmp/.doctest_boolean_function.py
 [5.3 s]

Component: doctest coverage

Author: Minh Van Nguyen

Reviewer: Jaap Spies

Merged: Sage 4.1.2.rc0

Issue created by migration from https://trac.sagemath.org/ticket/7020

[kcrisman]

comment:1

Either this patch or an identical one but with the other # (217 or 222) in the - line should apply and fix this. Probably it should be renamed as well!

[sagetrac-mvngu]

based on Sage 4.1.2.alpha4

[sagetrac-mvngu]

Changed author from Minh van Nguyen to Minh Van Nguyen

[sagetrac-mvngu]

comment:3

Attachment: trac_7020-bitness-issue.patch.gz

[jaapspies]

Reviewer: Jaap Spies

[jaapspies]

comment:4

Works for me on Fedora 11, 32 bit:

[jaap@paix sage-4.1.2.alpha4]$ ./sage -t  "devel/sage/sage/crypto/boolean_function.pyx"
sage -t  "devel/sage/sage/crypto/boolean_function.pyx"      
	 [8.9 s]
 
----------------------------------------------------------------------
All tests passed!
Total time for all tests: 8.9 seconds

[sagetrac-mvngu]

Merged: Sage 4.1.2.rc0