#25 execute.cpp doesn't compile

closed-works-for-me
nobody
None
5
2005-03-21
2004-06-18
Anonymous
No

The program compilation aborts while compiling
'scr/ri/execute.cpp'.

After few minutes compiling the above file, the system
used memory suddenly increases up to 100%, then the
same happens to the swap memory, then the compilation
aborts with the following error message:

g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I.. -g -O2 -MT
execute.lo -MD -MP -MF .deps/execute.Tpo -c execute.cpp
-fPIC -DPIC -o .libs/execute.o
g++: Internal error: Killed (program cc1plus)

This is the output from the 'ps -eflww' command:

0 S vector 13975 13155 0 69 0 - 454 wait4
13:37 pts/2 00:00:00 g++ -DHAVE_CONFIG_H -I. -I.
-I../.. -I.. -g -O1 -MT execute.lo -MD -MP -MF
.deps/execute.Tpo -c execute.cpp -fPIC -DPIC -o
.libs/execute.o
0 D vector 13976 13975 65 73 0 - 79791 lock_p
13:37 pts/2 00:01:27
/usr/lib/gcc-lib/i586-mandrake-linux-gnu/3.3.2/cc1plus
-quiet -I. -I. -I../.. -I.. -MD .libs/execute.d -MF
.deps/execute.Tpo -MP -MT execute.lo -MQ
.libs/execute.o -D__GNUC__=3 -D__GNUC_MINOR__=3
-D__GNUC_PATCHLEVEL__=2 -D_GNU_SOURCE -DHAVE_CONFIG_H
-DPIC execute.cpp -D__GNUG__=3 -quiet -dumpbase
execute.cpp -auxbase-strip .libs/execute o -g -O1 -fPIC
-o /home/vector/tmp/ccXXYhsA.s

This is the output from the 'lsof | grep cc1plus' command:

cc1plus 13299 vector cwd DIR 3,5 5536
88367 /home/vector/Pixie/src/ri
cc1plus 13299 vector rtd DIR 3,1 592
2 /
cc1plus 13299 vector txt REG 3,1 3797100
94413
/usr/lib/gcc-lib/i586-mandrake-linux-gnu/3.3.2/cc1plus
cc1plus 13299 vector mem REG 3,1 1223895
270 /lib/ld-2.3.3.so
cc1plus 13299 vector mem REG 3,1 57
180031
/usr/share/locale/en_US/LC_MESSAGES/SYS_LC_MESSAGES
cc1plus 13299 vector mem REG 3,5 23079
88857 /home/vector/Pixie/src/ri/execute.cpp
cc1plus 13299 vector mem REG 3,1 1322716
260 /lib/i686/libc-2.3.3.so
cc1plus 13299 vector mem REG 3,1 178476
4074 /usr/share/locale/ISO-8859-1/LC_CTYPE
cc1plus 13299 vector mem REG 3,1 12695
50959
/usr/lib/gcc-lib/i586-mandrake-linux-gnu/3.3.2/include/stddef.h
cc1plus 13299 vector mem REG 3,1 25060
32377 /usr/include/bits/mathinline.h
cc1plus 13299 vector mem REG 3,1 19049
32355 /usr/include/bits/confname.h
cc1plus 13299 vector mem REG 3,1 12922
33426 /usr/include/signal.h
cc1plus 13299 vector mem REG 3,5 25730
95894 /home/vector/Pixie/src/ri/scriptOpcodes.h
cc1plus 13299 vector mem REG 3,1 29184
33609 /usr/include/wchar.h
cc1plus 13299 vector mem REG 3,5 21483
95898 /home/vector/Pixie/src/ri/shaderOpcodes.h
cc1plus 13299 vector mem REG 3,5 33738
95893 /home/vector/Pixie/src/ri/scriptFunctions.h
cc1plus 13299 vector mem REG 3,5 74999
95896 /home/vector/Pixie/src/ri/shaderFunctions.h
cc1plus 13299 vector mem REG 3,5 37978
95872 /home/vector/Pixie/src/ri/giFunctions.h
cc1plus 13299 vector 0u CHR 136,1
3 /dev/pts/1
cc1plus 13299 vector 1u CHR 136,1
3 /dev/pts/1
cc1plus 13299 vector 2u CHR 136,1
3 /dev/pts/1
cc1plus 13299 vector 3w REG 3,5 0
96376 /home/vector/tmp/ccM92PDd.s
cc1plus 13299 vector 9u CHR 136,1
3 /dev/pts/1

I took a look at the offending source file but couldn't
do more than noticing that you're using a lot of
macros, maybe some loops running around the
"DEF*OPCODE" and "DEF*FUNC" ones? (just a guess from a
not-very-expert programmer-wannabe ;)

The system is a Mandrake 10.0 running on Athlon-XP cpu.

I hope my infos could help.

As a side note, I also hope that your project could
soon make its way into the Blender environment as I
personally like it most than the actual Yafray or the
proposed future Aqsis renderers and let me forget
peacefully BMRT (R.I.P. ;).

I also will like to be enrolled as beta tester if you
ever need it; this is my email: stardream AT tiscali
DOT it.

Regards,
Nicola Farina

Discussion

  • Okan Arikan

    Okan Arikan - 2004-06-25

    Logged In: YES
    user_id=555300

    Gcc 3.3 seems to have a memory problem which is
    creating this. execute.cpp is the shading language
    interpreter. In order to get absolute fastest execution, each
    instruction is defined as a macro. I'm still thinking ways of
    making execute.cpp, but it is not very easy.

    I believe Pixie is compatible with BlenderMan. sutabi
    seems to use Pixie with Blender this way. I will investigate
    the compatibility and perhaps create a tutorial.

    Any contribution is welcome. Your bug reports will be
    greatly appreciated.

    Thanks

    Okan

     
  • George Harker

    George Harker - 2005-03-21

    Logged In: YES
    user_id=995400

    gcc requires a lot of memory and a fairly long time to compile this file.
    Known to work with gcc versions 2.95 3.2 3.3.

     
  • George Harker

    George Harker - 2005-03-21
    • status: open --> open-works-for-me
     
  • George Harker

    George Harker - 2005-03-21
    • status: open-works-for-me --> closed-works-for-me
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks