Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 81908 - gcc crashed when compiling xorg-x11 on amd64
Summary: gcc crashed when compiling xorg-x11 on amd64
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GCC Porting (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Please assign to toolchain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-13 14:00 UTC by Bruno Lustosa
Modified: 2005-03-26 18:32 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Bruno Lustosa 2005-02-13 14:00:45 UTC 
Sometimes, when emerging packages, I get an internal compiler error, and am asked to submit a full bug report. I've never done that, because normally if I retry, it will work fine.
I'm not sure if this is a hardware problem (segmentation fault can be), but the message states that it can be an OS problem.

Reproducible: Sometimes
Steps to Reproduce:
1.
2.
3.




This was the error I got when trying to compile xorg-x11.

make[7]: Entering directory
`/var/tmp/portage/xorg-x11-6.8.2/work/xc/programs/Xserver/GL/mesa/main'
rm -f dispatch.o
x86_64-pc-linux-gnu-gcc -march=athlon64 -O2 -pipe -fomit-frame-pointer
-fno-strict-aliasing -ansi -pedantic -Wno-return-type -w  -fno-merge-constants
-I../../../../../extras/Mesa/src/mesa            
-I../../../../../extras/Mesa/src/mesa/main             
-I../../../../../extras/Mesa/src/mesa/shader             
-I../../../../../extras/Mesa/src/mesa/glapi            
-I../../../../../extras/Mesa/include                
-I../../../../../programs/Xserver/include -I../../../../../exports/include/X11
-I../../../../../programs/Xserver/GL/include
-I../../../../../programs/Xserver/GL/glx                
-I../../../../../lib/GL/include                
-I../../../../../programs/Xserver/hw/xfree86 -I../../../../../exports/include 
-I../../../../.. -I../../../../../exports/include   -Dlinux -D__amd64__
-D_POSIX_C_SOURCE=199309L                              -D_POSIX_SOURCE
-D_XOPEN_SOURCE  -D_BSD_SOURCE -D_SVID_SOURCE                             
-D_GNU_SOURCE                           -DSHAPE -DXINPUT -DXKB -DLBX -DXAPPGROUP
        -DXCSECURITY -DTOGCUP   -DXF86BIGFONT -DDPMSExtension     -DPANORAMIX  
 -DRENDER -DRANDR       -DXFIXES -DDAMAGE -DCOMPOSITE -DXEVIE      -DGCCUSESGAS
-DAVOID_GLYPHBLT -DPIXPRIV -DSINGLEDEPTH                          -DXFreeXDGA
-DXvExtension-DXFree86LOADER  -DXFree86Server                                
-DXF86VIDMODE                           -DXvMCExtension         
-DSMART_SCHEDULE                                  -DXResExtension              
                 -DX_BYTE_ORDER=X_LITTLE_ENDIAN   -DXORG_VERSION_CURRENT="(((6)
* 10000000) + ((8) * 100000) + ((2) * 1000) + 0)" -D_XSERVER64 -DNDEBUG  
-DFUNCPROTO=15 -DNARROWPROTO  -DIN_MODULE -DXFree86Module -DGLXEXT -DXF86DRI
-DGLX_DIRECT_RENDERING -DGLX_USE_DLOPEN -DGLX_USE_MESA -D__GLX_ALIGN64   -c
dispatch.c
../../../../../extras/Mesa/src/mesa/glapi/glapitemp.h: In function
`glVertexAttrib4uivARB':
../../../../../extras/Mesa/src/mesa/glapi/glapitemp.h:3367: 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 reproducible, so it is likely a hardware or OS problem.
make[7]: *** [dispatch.o] Error 1
make[7]: Leaving directory
`/var/tmp/portage/xorg-x11-6.8.2/work/xc/programs/Xserver/GL/mesa/main'



This is the info from 'emerge info'.

Portage 2.0.51-r15 (default-linux/amd64/2004.3, gcc-3.4.3,
glibc-2.3.4.20041102-r0, 2.6.10-gentoo-r6 x86_64)
=================================================================
System uname: 2.6.10-gentoo-r6 x86_64 AMD Athlon(tm) 64 Processor 3000+
Gentoo Base System version 1.6.9
Python:              dev-lang/python-2.3.4-r1 [2.3.4 (#1, Feb  8 2005, 14:52:59)]
dev-lang/python:     2.3.4-r1
sys-devel/autoconf:  2.59-r6, 2.13
sys-devel/automake:  1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.4
sys-devel/binutils:  2.15.92.0.2-r2
sys-devel/libtool:   1.5.10-r4
virtual/os-headers:  2.6.8.1-r3
ACCEPT_KEYWORDS="amd64 ~amd64"
AUTOCLEAN="yes"
CFLAGS="-march=athlon64 -O2 -pipe -fomit-frame-pointer"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config
/usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/
/usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/
/usr/share/texmf/xdvi/ /var/bind /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=athlon64 -O2 -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox"
GENTOO_MIRRORS="http://open-systems.ufl.edu/mirrors/gentoo
http://mirror.datapipe.net/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="amd64 16bit X aac acpi acpi4linux aim alsa apache2 asm avi bash-completion
berkdb bitmap-fonts bluetooth bonobo bzlib cdr crypt cups dga divx4linux dvd esd
exif f77 fam font-server fortran ftp gd gdbm gif gnome gphoto2 gstreamer gtk
gtk2 gtkhtml guile icq imagemagick imlib jabber java jp2 jpeg libwww lzw
lzw-tiff maildir mikmod mozilla moznocompose moznoirc moznomail mpeg msn
multilib ncurses nls nvidia offensive ogg oggvorbis opengl oss pam perl png
readline sasl sdl ssl tcpd tetex tiff truetype truetype-fonts type1-fonts usb
userlocales xml xml2 xmms xpm xrandr xv xvid yahoo zlib"
Unset:  ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, PORTDIR_OVERLAY
Comment 1 Bruno Lustosa 2005-02-14 06:05:59 UTC 
Additionally, I had to try the compiling of xorg-x11 at least 5 times before it would finish. Error was always the same, though not in the same place.
Comment 2 SpanKY gentoo-dev 2005-02-14 06:24:13 UTC 
from your description, this sounds like hardware ...

i'd load up memtest and test your RAM ... you should also double check that the cpu is properly cooled ...
Comment 3 Bruno Lustosa 2005-02-14 07:49:15 UTC 
Yes, I know this can be hardware, but I thought it could be some issue with the compiler. Not sure if amd64 has been tested as thoroughly as x64.
Anyway, I loaded memtest86 as soon as I bought the machine (it's 2 months old), and as far as I see, the cpu is properly cooled (48 celsius). The processor is an Athlon64 3000+.
Anyway, I can work around the bug easily, but thought someone could want to have a look at. If I can give any extra information, please tell me.
Thank you.
Comment 4 Bruno Lustosa 2005-03-26 18:32:06 UTC 
I'm invalidating this, as I got more evidence that this could really be a hardware issue.