Bug in CUDA 2.3 64-bit toolkit: wrong nvcc.profile

Accelerated Computing CUDA CUDA Programming and Performance
1

The nvcc.profile in /CUDA/bin64 incorrectly adds $(TOP)/bin to $PATH, which means 64-bit nvcc ends up calling the 32-bit cudafe in /CUDA/bin/cudafe. In my case at least this causes cudafe to fail with an internal assertion error:

Internal error: assertion failed at: “D:/Bld/rel/gpgpu/toolkit/r2.3/compiler/edg/EDG_3.9/src/c_gen_be.c”, line 3398
1 catastrophic error detected in the compilation of “converter-kernels.cpp1.ii”.
Compilation aborted.

If I fix nvcc.profile to use $TOP/bin64 it all works OK (or if I remove the 32-bit cudafe.exe, then it finds the 64-bit one in the inherited $PATH). Of course I would rather not have to patch all my installs of the CUDA toolkit; is there an official fix for this, or is there a hidden nvcc option to use a different .profile file?

2

You are correct: this is a bug in nvcc.profile. Someone reported it a few weeks ago, but unfortunately it was already too late to make it in to the CUDA 3.0 Toolkit.

Your change is essentially fine. Alternatively, if you add c:\cuda\bin64 to your system PATH environment variable, it should work even without changing nvcc.profile.

–Cliff

3

I tried that, but apparently the .profile prepends, so it preferentially uses the wrong cudafe even if c:\cuda\bin64 is in my system PATH.

I’ll continue using my fix.

4

I have the same problem (2.3 version):

but I have 64-bit SDK/toolkit only. Earlier I compiled all without problems, today - I can’t. I didn’t change sourcecode, drivers etc.

So I reinstalled drivers, SDK and toolkit - nothing.

5

I have the same problem (2.3 version):

but I have 64-bit SDK/toolkit only. Earlier I compiled all without problems, today - I can’t. I didn’t change sourcecode, drivers etc.

So I reinstalled drivers, SDK and toolkit - nothing.