gcc -c -O3 -march=athlon-xp -fomit-frame-pointer -W -Wall -DHAVE_CONFIG_H -I. -I. -I../include -I../include -DPATH_SANE_CONFIG_DIR=/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/share -DV_MAJOR=1 -DV_MINOR=0 -DSTUBS -DBACKEND_NAME=umax umax-s.c -fPIC -DPIC -o .libs/umax-s.o gcc -shared .libs/umax.o .libs/umax-s.o .libs/sane_strstatus.o ../sanei/.libs/sanei_init_debug.o ../sanei/.libs/sanei_config.o ../lib/.libs/alloca.o ../sanei/.libs/sanei_config2.o ../sanei/.libs/sanei_constrain_value.o ../sanei/.libs/sanei_scsi.o ../sanei/.libs/sanei_usb.o ../sanei/.libs/sanei_pv8630.o -lnsl -lm /usr/lib/libjpeg.so /usr/lib/libieee1284.so -ldl -Wl,-soname -Wl,libsane.so.1 -o .libs/libsane-umax.so.1.0.13 (cd .libs && rm -f libsane-umax.so.1 && ln -s libsane-umax.so.1.0.13 libsane-umax.so.1) (cd .libs && rm -f libsane-umax.so && ln -s libsane-umax.so.1.0.13 libsane-umax.so) creating libsane-umax.la (cd .libs && rm -f libsane-umax.la && ln -s ../libsane-umax.la libsane-umax.la) gcc -c -O3 -march=athlon-xp -fomit-frame-pointer -W -Wall -DHAVE_CONFIG_H -I. -I. -I../include -I../include -DPATH_SANE_CONFIG_DIR=/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/share -DV_MAJOR=1 -DV_MINOR=0 -DBACKEND_NAME=umax_pp_low -DLIBDIR=/usr/lib/sane umax_pp_low.c -fPIC -DPIC -o .libs/umax_pp_low.o umax_pp_low.c: In function `sanei_umax_pp_ProbeScanner': umax_pp_low.c:6058: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://bugs.gentoo.org/> for instructions. The bug is not reproduceable, so it is likely a hardware or OS problem make[1]: *** [umax_pp_low.lo] Ошибка 1 make[1]: Leaving directory `/var/tmp/portage/sane-backends-1.0.13-r3/work/sane-backends-1.0.13/backend' make: *** [all-recursive] Ошибка 1 !!! ERROR: media-gfx/sane-backends-1.0.13-r3 failed. !!! Function src_compile, Line 49, Exitcode 2 !!! (no error message) Reproducible: Always Steps to Reproduce: 1. 2. 3. If change -O3 to -O2 emerge works ok.
Please provide the "emerge info" output.
Are you able to reproduce this bug, make it segfault every time at the same file and same code line? If no, it's likely that you have a hardware problem. At least I can't reproduce your error with the same CFLAGS and gcc 3.3.2.
No reaction, assuming hardware problems.