Always use the value of rebuild_strict
Add test
Fix test
Merge pull request #1343 from lamblin/fix_rebuild_strict

Always use the value of rebuild_strict
Removed a misleading comment.

The value added to a_i (result of multiplication i_d*a_str[d]) was unsigned int, which broke when strides were negative.
This is not a bug in nvcc 3.0, it is correct behavior according to the C99 standard:

"Otherwise, if the operand that has unsigned integer type has rank greater or equal to the rank of the type of the other operand, then the operand with signed integer type is converted to the type of the operand with unsigned integer type."
Add a benchmark result for the GTX 650 Ti and add spaces in the card names so that this file can more easily be found when searching (via grep, Google, etc.) using the real names
Merge pull request #1352 from benmccann/checkblas

Add a benchmark result for the GTX 650 Ti
Merge pull request #1350 from temporaer/minor

Removed a misleading comment.
make sparse Arctanh gradient test more stable.

Otherwise, it was failing due to numerial problem in some case.
Merge pull request #1354 from nouiz/more_stable_test

make sparse Arctanh gradient test more stable.
Better wording for some documentation
PEP8 (fixed a line too long)
Fixed some typos and improved wording
PEP8