You are not logged in.

#1 2009-06-02 04:59:51

gajo
Member
Registered: 2008-04-01
Posts: 93
Website

[SOLVED]CUDA - problem compiling files

I'm having some problem with nvcc (that's part of cuda-toolkit).
I'm using 64bit arch (obviously), and I'm trying to compile it with nvcc -m64  -c  cudaIntegralsFloat.cu  . I've tried it without -m64, with -Xopencc -O2, withotu any of it, with -g, and all the combinations had the same effect, it would seg fault with this or very similar core dump.
I can't tell the difference anyway.
I'm also using nvidia-beta and nvidia-utils-beta, as well as cuda-sdk all of which are from AUR. I have a 8800 GT card, and previously (cuda 2.1) compiled programs (the cudaIntegralsFloat mentioned in the command line below), alongside with those that come with cuda-sdk work just fine now (oddly, they didn't work with 2.1, were seg faulting or some such thing, but that's another thing, of the past hopefully).
The core dump :

nvcc -g --host-compilation C++  -c  cudaIntegralsFloat.cu
/tmp/tmpxft_00005a05_00000000-7_cudaIntegralsFloat.cpp3.i(0): Warning: Olimit was exceeded on function _Z8getPRIntPfS_im; will not perform function-scope optimization.
    To still perform function-scope optimization, use -OPT:Olimit=0 (no limit) or -OPT:Olimit=56329

### Assertion failure at line 2520 of ../../be/cg/NVISA/cgtarget.cxx:
### Compiler Error in file /tmp/tmpxft_00005a05_00000000-7_cudaIntegralsFloat.cpp3.i during Register Allocation phase:
### ran out of registers in integer
*** glibc detected *** /usr/lib//be: free(): invalid pointer: 0x000000000293efe0 ***
======= Backtrace: =========
/lib/libc.so.6[0x2ac444f16a76]
/lib/libc.so.6(cfree+0x6c)[0x2ac444f1b44c]
/usr/lib//be[0x5b7275]
/lib/libc.so.6[0x2ac444ed9e12]
/lib/libc.so.6[0x2ac444ed9e75]
/usr/lib//be[0x6a4c70]
/usr/lib//be[0x5245e3]
/usr/lib//be[0x524694]
/usr/lib//be[0x5366c5]
/usr/lib//be[0x4052bd]
/usr/lib//be[0x406081]
/usr/lib//be[0x4073ad]
/lib/libc.so.6(__libc_start_main+0xfd)[0x2ac444ec39ed]
/usr/lib//be[0x4037ea]
======= Memory map: ========
00400000-0080c000 r-xp 00000000 08:01 252690                             /usr/lib/be
0090b000-0092f000 rw-p 0040b000 08:01 252690                             /usr/lib/be
0092f000-00bfa000 rw-p 0092f000 00:00 0 
02594000-05f66000 rw-p 02594000 00:00 0                                  [heap]
2ac4444c1000-2ac4444de000 r-xp 00000000 08:01 140223                     /lib/ld-2.10.1.so
2ac4444de000-2ac4444e0000 rw-p 2ac4444de000 00:00 0 
2ac4446dd000-2ac4446de000 r--p 0001c000 08:01 140223                     /lib/ld-2.10.1.so
2ac4446de000-2ac4446df000 rw-p 0001d000 08:01 140223                     /lib/ld-2.10.1.so
2ac4446df000-2ac4447d0000 r-xp 00000000 08:01 81846                      /usr/lib/libstdc++.so.6.0.11
2ac4447d0000-2ac4449d0000 ---p 000f1000 08:01 81846                      /usr/lib/libstdc++.so.6.0.11
2ac4449d0000-2ac4449d7000 r--p 000f1000 08:01 81846                      /usr/lib/libstdc++.so.6.0.11
2ac4449d7000-2ac4449d9000 rw-p 000f8000 08:01 81846                      /usr/lib/libstdc++.so.6.0.11
2ac4449d9000-2ac4449ee000 rw-p 2ac4449d9000 00:00 0 
2ac444a0c000-2ac444a8d000 r-xp 00000000 08:01 140250                     /lib/libm-2.10.1.so
2ac444a8d000-2ac444c8c000 ---p 00081000 08:01 140250                     /lib/libm-2.10.1.so
2ac444c8c000-2ac444c8d000 r--p 00080000 08:01 140250                     /lib/libm-2.10.1.so
2ac444c8d000-2ac444c8e000 rw-p 00081000 08:01 140250                     /lib/libm-2.10.1.so
2ac444c8e000-2ac444ca4000 r-xp 00000000 08:01 81865                      /usr/lib/libgcc_s.so.1
2ac444ca4000-2ac444ea3000 ---p 00016000 08:01 81865                      /usr/lib/libgcc_s.so.1
2ac444ea3000-2ac444ea4000 rw-p 00015000 08:01 81865                      /usr/lib/libgcc_s.so.1
2ac444ea4000-2ac444ea5000 rw-p 2ac444ea4000 00:00 0 
2ac444ea5000-2ac444ff0000 r-xp 00000000 08:01 140254                     /lib/libc-2.10.1.so
2ac444ff0000-2ac4451f0000 ---p 0014b000 08:01 140254                     /lib/libc-2.10.1.so
2ac4451f0000-2ac4451f4000 r--p 0014b000 08:01 140254                     /lib/libc-2.10.1.so
2ac4451f4000-2ac4451f5000 rw-p 0014f000 08:01 140254                     /lib/libc-2.10.1.so
2ac4451f5000-2ac4451fc000 rw-p 2ac4451f5000 00:00 0 
2ac446060000-2ac446062000 rw-p 2ac446060000 00:00 0 
2ac446f52000-2ac44e967000 rw-p 2ac446f52000 00:00 0 
2ac450000000-2ac450021000 rw-p 2ac450000000 00:00 0 
2ac450021000-2ac454000000 ---p 2ac450021000 00:00 0 
7fff6649b000-7fff665e8000 rw-p 7fffffeb2000 00:00 0                      [stack]
7fff665fe000-7fff665ff000 r-xp 7fff665fe000 00:00 0                      [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                  [vsyscall]
Signal: Aborted in Register Allocation phase.
<input>(0): Error: Signal Aborted in phase Register Allocation -- processing aborted
*** Internal stack backtrace:
    /usr/lib//be [0x6a350f]
    /usr/lib//be [0x6a4159]
    /usr/lib//be [0x6a38ad]
    /usr/lib//be [0x6a4af6]
    /lib/libc.so.6 [0x2ac444ed7350]
    /lib/libc.so.6(gsignal+0x35) [0x2ac444ed72d5]
    /lib/libc.so.6(abort+0x19a) [0x2ac444ed873a]
    /lib/libc.so.6 [0x2ac444f114ad]
    /lib/libc.so.6 [0x2ac444f16a76]
    /lib/libc.so.6(cfree+0x6c) [0x2ac444f1b44c]
    /usr/lib//be [0x5b7275]
    /lib/libc.so.6 [0x2ac444ed9e12]
    /lib/libc.so.6 [0x2ac444ed9e75]
    /usr/lib//be [0x6a4c70]
    /usr/lib//be [0x5245e3]
    /usr/lib//be [0x524694]
    /usr/lib//be [0x5366c5]
    /usr/lib//be [0x4052bd]
    /usr/lib//be [0x406081]
    /usr/lib//be [0x4073ad]
    /lib/libc.so.6(__libc_start_main+0xfd) [0x2ac444ec39ed]
    /usr/lib//be [0x4037ea]
nvopencc INTERNAL ERROR: /usr/lib//be died due to signal 4
make: *** [cudaIntegralsFloat.o] Error 255

I'm thinking that some ln -s was lacking during install and this is the end result... but I really have no idea

Last edited by gajo (2009-06-03 08:23:04)

Offline

#2 2009-06-03 08:22:45

gajo
Member
Registered: 2008-04-01
Posts: 93
Website

Re: [SOLVED]CUDA - problem compiling files

I've managed to fix it by appending --opencc-options -OPT:Olimit=99999 to nvcc's compiling flags. It compiles and executes fine. Even though that's still a bug (no program should seg fault).

Offline

Board footer

Powered by FluxBB