Fix a (potential) bug from CUDA 6.5 to CUDA 7.0

``Potential'' means that this is probably not a bug on SPIKE side,
but a bug on CUDA 7.0 side, OR the change of executing model in
CUDA 7.0