This error occurred when building the Crystal Space package from CVS (Januari 8th). make all *-------------------------------------------------------------------------* Building CrystalClear entity library Building for LINUX/GCC/INTEL in optimize mode *-------------------------------------------------------------------------* make[1]: Nothing to be done for `csclearlib'. *-------------------------------------------------------------------------* Building Crystal Space 3D engine Building for LINUX/GCC/INTEL in optimize mode *-------------------------------------------------------------------------* gcc -c -o out/LINUX/INTEL/optimize/camera.o libs/csengine/camera.cpp -Wall -Wunused -W -mpentiumpro -march=i686 -fno-exceptions -fno-rtti -O6 -fomit-frame-pointer -ffast-math -I. -I./apps -I./include -I./libs -I./plugins -I./support libs/csengine/camera.cpp: In method `void csCamera::LookAt (const csVector3 &, const csVector3 &)': libs/csengine/camera.cpp:163: Internal compiler error in emit_swap_insn , at reg-stack.c:965 Please submit a full bug report. See <URL:http://bugzilla.redhat.com/bugzilla/> for instructions. make[1]: *** [out/LINUX/INTEL/optimize/camera.o] Error 1 make: *** [csengine] Error 2
I forgot some (maybe important) information: processor: AMD-Athlon 750Mhz mem: 128M Linux Kernel: 2.4.0-test8
Please rerun gcc -c -o out/LINUX/INTEL/optimize/camera.o libs/csengine/camera.cpp -Wall -Wunused -W -mpentiumpro -march=i686 -fno-exceptions -fno-rtti -O6 -fomit-frame-pointer -ffast-math -I. -I./apps -I./include -I./libs -I./plugins -I./support -save-temps -v and attach here camera.ii it creates.
Created attachment 7464 [details] This is the output gcc generates with the additional -save-temps -v flags
The constraints in include/qsqrt.h are bogus, you cannot request ret be returned in st while at the same time requesting it not to be returned in st. Removing "st" from the list of clobbers should fix this. As for why gcc segfaults on this, it should not but gcc previously did even less checking of the correctness of asm constraints, so I definitely don't consider it high priority for fixing.
*** Bug 25162 has been marked as a duplicate of this bug. ***