Compiler error with GCC 4.8.1

[mschatz]

Im trying to compile using GCC 4.8.1, but it keeps crashing with an internal compiler error in kyotocabinet (see below). Is anyone able to compile with this? It also crashed (in a different way) with GCC 4.4.6. Has anyone been able to compile and run on Red Hat Enterprise Linux Server release 6.4 (Santiago)?

Thank you,

Mike

note this also crashes without specifying c99 as well:

$ CFLAGS=-std=c99 make

...

g++ -c -I. -I/bluearc/data/schatz/software/packages/progressiveCactus/progressiveCactus/submodules/kyotocabinet/include -I/usr/local/include -DNDEBUG -D_GNU_SOURCE=1 -D_FILE_OFFSET_BITS=64 -D_REENTRANT -D__EXTENSIONS__ -D_MYZLIB -D_MYGCCATOMIC -D_KC_PREFIX=""/bluearc/data/schatz/software/packages/progressiveCactus/progressiveCactus/submodules/kyotocabinet"" -D_KC_INCLUDEDIR=""/bluear c/data/schatz/software/packages/progressiveCactus/progressiveCactus/submodules/kyotocabinet/include"" -D_KC_LIBDIR=""/bluearc/data/schatz/software/packages/progressiveCactus/progressiveCactus/submodules/kyotocabinet/lib"" -D_KC_BINDIR=""/bluearc/data/schatz/software/packages/progressiveCactus/progressiveCactus/submodules/kyotocabinet/bin"" -D_KC_LIBEXECDIR=""/bluearc/data/schatz/software/packages/progressiveCactus/progressiveCactus/submodules/kyotocabinet/libexec"" -D_KC_APPINC=""-I/bluearc/data/schatz/software/packages/progressiveCactus/progressiveCactus/submodules/kyotocabinet/include"" -D_KC_APPLIBS=""-L/bluearc/data/schatz/software/packages/progressiveCactus/progressiveCactus/submodules/kyotocabinet/lib -lkyotocabinet -lz -lstdc++ -lrt -lpthread -lm -lc "" -march=native -m64 -O3 -g -Wall -funroll-loops -DNDEBUG -I /bluearc/data/schatz/software/packages/progressiveCactus/progressiveCactus/submodules/sonLib/lib -I /bluearc/data/schatz/software/packages/progressiveCactus/progressiveCactus/submodules/tokyocabinet/include -DHAVE_TOKYO_CABINET=1 -I/bluearc/data/schatz/software/packages/progressiveCactus/progressiveCactus/submodules/kyotocabinet/include -I/bluearc/data/schatz/software/packages/progressiveCactus/progressiveCactus/submodules/kyototycoon/include -DHAVE_KYOTO_TYCOON=1 -I/bluearc/data/schatz/software/packages/progressiveCactus/progressiveCactus/submodules/zlib/include -I/usr/local/gcc4/include -L/usr/local/gcc4/lib64 -L/usr/local/gcc4/lib -Wall -fPIC -fsigned-char -g0 -O2 -Wno-unused-but-set-variable -Wno-unused-but-set-parameter kcpolydb.cc g++: internal compiler error: Killed (program cc1plus) 0x409a71 execute ../../gcc/gcc.c:2823 0x409db4 do_spec_1 ../../gcc/gcc.c:4615 0x40c735 process_brace_body ../../gcc/gcc.c:5872 0x40c735 handle_braces ../../gcc/gcc.c:5786 0x40acd7 do_spec_1 ../../gcc/gcc.c:5269 0x40c735 process_brace_body ../../gcc/gcc.c:5872 0x40c735 handle_braces ../../gcc/gcc.c:5786 0x40acd7 do_spec_1 ../../gcc/gcc.c:5269 x40c735 process_brace_body ../../gcc/gcc.c:5872 0x40c735 handle_braces ../../gcc/gcc.c:5786 0x40acd7 do_spec_1 ../../gcc/gcc.c:5269 0x40c735 process_brace_body ../../gcc/gcc.c:5872 0x40c735 handle_braces ../../gcc/gcc.c:5786 0x40acd7 do_spec_1 ../../gcc/gcc.c:5269 0x40c735 process_brace_body ../../gcc/gcc.c:5872 0x40c735 handle_braces ../../gcc/gcc.c:5786 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See http://gcc.gnu.org/bugs.html for instructions. make[2]: *** [kcpolydb.o] Error 4 make[2]: Leaving directory /bluearc/data/schatz/software/packages/progressiveCactus/progressiveCactus/submodules/kyotocabinet' make[1]: *** [kyotocabinetRule] Error 2 make[1]: Leaving directory/bluearc/data/schatz/software/packages/progressiveCactus/progressiveCactus/submodules' make: *** [all] Error 2

[joelarmstrong]

It looks like this might be a known bug in GCC 4.8.1 (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58088), but weirdly enough I can't reproduce it with the same version & command as you. Maybe it has to do with different libstdc++ versions or something.

I don't really know if there's a workaround for getting 4.8.1 to work. What's the error that gcc 4.4.6 gives?

PS: you may also want to try seeing if it compiles successfully with -O0 instead, but that's a long shot.

[mschatz]

Thank you for looking at it.

Here is the error I get from 4.4.6:

make

...

g++ -c -I. -I/bluearc/data/schatz/software/packages/progressiveCactus/progressiveCactus/submodules/kyotocabinet/include -I/usr/local/include -DNDEBUG -D_GNU_SOURCE=1 -D_FILE_OFFSET_BITS=64 -D_REENTRANT -D__EXTENSIONS__ -D_MYZLIB -D_MYGCCATOMIC -D_KC_PREFIX=""/bluearc/data/schatz/software/packages/progressiveCactus/progressiveCactus/submodules/kyotocabinet"" -D_KC_INCLUDEDIR=""/bluearc/data/schatz/software/packages/progressiveCactus/progressiveCactus/submodules/kyotocabinet/include"" -D_KC_LIBDIR=""/bluearc/data/schatz/software/packages/progressiveCactus/progressiveCactus/submodules/kyotocabinet/lib"" -D_KC_BINDIR=""/bluearc/data/schatz/software/packages/progressiveCactus/progressiveCactus/submodules/kyotocabinet/bin"" -D_KC_LIBEXECDIR=""/bluearc/data/schatz/software/packages/progressiveCactus/progressiveCactus/submodules/kyotocabinet/libexec"" -D_KC_APPINC=""-I/bluearc/data/schatz/software/packages/progressiveCactus/progressiveCactus/submodules/kyotocabinet/include"" -D_KC_APPLIBS=""-L/bluearc/data/schatz/software/packages/progressiveCactus/progressiveCactus/submodules/kyotocabinet/lib -lkyotocabinet -lz -lstdc++ -lrt -lpthread -lm -lc "" -march=native -m64 -O3 -g -Wall -funroll-loops -DNDEBUG -I /bluearc/data/schatz/software/packages/progressiveCactus/progressiveCactus/submodules/sonLib/lib -I /bluearc/data/schatz/software/packages/progressiveCactus/progressiveCactus/submodules/tokyocabinet/include -DHAVE_TOKYO_CABINET=1 -I/bluearc/data/schatz/software/packages/progressiveCactus/progressiveCactus/submodules/kyotocabinet/include -I/bluearc/data/schatz/software/packages/progressiveCactus/progressiveCactus/submodules/kyototycoon/include -DHAVE_KYOTO_TYCOON=1 -I/bluearc/data/schatz/software/packages/progressiveCactus/progressiveCactus/submodules/zlib/include -I/usr/local/gcc4/include -L/usr/local/gcc4/lib64 -L/usr/local/gcc4/lib -Wall -fPIC -fsigned-char -g0 -O2 -Wno-unused-but-set-variable -Wno-unused-but-set-parameter kcdbext.cc g++: Internal error: Killed (program cc1plus) Please submit a full bug report. See http://bugzilla.redhat.com/bugzilla for instructions. make[2]: *** [kcdbext.o] Error 1 make[2]: Leaving directory /bluearc/data/schatz/software/packages/progressiveCactus/progressiveCactus/submodules/kyotocabinet' make[1]: *** [kyotocabinetRule] Error 2 make[1]: Leaving directory /bluearc/data/schatz/software/packages/progressiveCactus/progressiveCactus/submodules' make: *** [all] Error 2 bnbdev1:16:45:02:/bluearc/data/schatz/software/packages/progressiveCactus $ gcc --version gcc (GCC) 4.4.6 20110731 (Red Hat 4.4.6-3) Copyright (C) 2010 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Any tips would be appreciated.

Thank you,

Mike

On Wed, Oct 22, 2014 at 8:59 AM, Joel Armstrong [email protected] wrote:

It looks like this might be a known bug in GCC 4.8.1 ( https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58088), but weirdly enough I can't reproduce it with the same version & command as you. Maybe it has to do with different libstdc++ versions or something.

I don't really know if there's a workaround for getting 4.8.1 to work. What's the error that gcc 4.4.6 gives?

— Reply to this email directly or view it on GitHub https://github.com/glennhickey/progressiveCactus/issues/28#issuecomment-60080286 .

[joelarmstrong]

Sorry for the long delay in replying. I'm a bit stumped. I tried gcc 4.4.6 shortly after your last message and still didn't gotten the same error. This must be related to some header file or something that's different between our setups.

The only advice I can think of is to try to compile kyotocabinet on another machine and move the object files over to the machine you're having trouble on. That could possibly fix things.

Unfortunately we rely on libraries like kyotocabinet and kyototycoon that seem to be difficult to compile for some systems. In the next week or so I will try to find time to build a statically-compiled version of progressiveCactus that I can point people to when they have problems.

[mschatz]

Thanks for checking, I really appreciate it. I'll try to push our IT to install a newer version of GCC that doesnt have the internal compiler error.

Thanks again,

Mike

On Wed, Oct 29, 2014 at 4:21 PM, Joel Armstrong [email protected] wrote:

Sorry for the long delay in replying. I'm a bit stumped. I tried gcc 4.4.6 shortly after your last message and still didn't gotten the same error. This must be related to some header file or something that's different between our setups.

The only advice I can think of is to try to compile kyotocabinet on another machine and move the object files over to the machine you're having trouble on. That could possibly fix things.

Unfortunately we rely on libraries like kyotocabinet and kyototycoon that seem to be difficult to compile for some systems. In the next week or so I will try to find time to build a statically-compiled version of progressiveCactus that I can point people to when they have problems.

— Reply to this email directly or view it on GitHub https://github.com/glennhickey/progressiveCactus/issues/28#issuecomment-60997599 .