Warning Compiling in GPU Mode

[GoogleCodeExporter]

What steps will reproduce the problem?

1.make GPU=true
2.
3.

What is the expected output? What do you see instead?

To compile without errors, compile with warnings about pointers

What version of the product are you using? On what operating system?

Original truecrack & truecrack-optimized    ubuntu 10.10 & 12.04

Please provide any additional information below.

make GPU=true
cat Cuda/CudaCore.cu > Cuda.cu 
cat Cuda/CudaPkcs5.cu >> Cuda.cu
cat Cuda/CudaRmd160.cu >> Cuda.cu
cat Cuda/CudaAes.cu >> Cuda.cu
cat Cuda/CudaXts.cu >> Cuda.cu
/usr/local/cuda/bin/nvcc -c Cuda.cu -I./Common/ -I./Crypto/ -I./Cuda/ -I./Main/ 
-I./ -lm -D_GPU_ --opencc-options -OPT:Olimit=0  -o Cuda.o
./Cuda.cu(189): Warning: Cannot tell what pointer points to, assuming global 
memory space
./Cuda.cu(196): Warning: Cannot tell what pointer points to, assuming global 
memory space
./Cuda.cu(189): Warning: Cannot tell what pointer points to, assuming global 
memory space
./Cuda.cu(196): Warning: Cannot tell what pointer points to, assuming global 
memory space
./Cuda.cu(1164): Warning: Cannot tell what pointer points to, assuming global 
memory space

Compiling in GPU=false does not produce these warnings

Original issue reported on code.google.com by yehshuam...@gmail.com on 25 Nov 2012 at 10:45

[GoogleCodeExporter]

The warnings depend by the cuda compiler and the implementation of RIPEMD160 
algorithm in Truecrypt sources. If you compile TrueCrack in CPU mode, you use 
the standard gcc compiler but you don't use the acceleration provided by GPU, 

Original comment by luck87 on 5 Jan 2013 at 12:40

• Changed state: Done
• Added labels: ****
• Removed labels: ****