breaks on XFree86 build at -O2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gcc-3.3 (Ubuntu) |
Invalid
|
Critical
|
Matthias Klose |
Bug Description
With -O2, gcc sometimes produces files that have truncated symbols; given the
buildds are OK, this may be a local problem, but it is 100% reproducible on
certain files within the XFree86 tree:
daniels@
make
gcc -m32 -g -O2 -fno-strict-
-Wstrict-prototypes -Wmissing-
-Wmissing-
-Wnested-externs -Wundef -I../..
-I../..
-D_SVID_SOURCE -D_GNU_SOURCE
-DFUNCPROTO=15 -DNARROWPROTO -c -o keytypes.o keytypes.c
rm -f xkbcomp
gcc -m32 -o xkbcomp -g -O2 -fno-strict-
-Wpointer-arith -Wstrict-prototypes -Wmissing-
-Wmissing-
-Wnested-externs -Wundef -L../../exports/lib xkbcomp.o xkbscan.o expr.o
vmod.o indicators.o misc.o alias.o keymap.o keycodes.o keytypes.o
compat.o action.o symbols.o geometry.o xkbpath.o listing.o
xkbparse.o parseutils.o utils.o -lxkbfile -lXext -lX11
-Wl,-rpath-
keytypes.o: could not read symbols: File truncated
collect2: ld returned 1 exit status
make: *** [xkbcomp] Error 1
daniels@
rm keytypes.o
daniels@
gcc -m32 -g -fno-strict-
-Wstrict-prototypes -Wmissing-
-Wmissing-
-Wnested-externs -Wundef -I../..
-I../..
-D_SVID_SOURCE -D_GNU_SOURCE
-DFUNCPROTO=15 -DNARROWPROTO -c -o keytypes.o keytypes.c
daniels@
make xkbcomp
rm -f xkbcomp
gcc -m32 -o xkbcomp -g -O2 -fno-strict-
-Wpointer-arith -Wstrict-prototypes -Wmissing-
-Wmissing-
-Wnested-externs -Wundef -L../../exports/lib xkbcomp.o xkbscan.o expr.o
vmod.o indicators.o misc.o alias.o keymap.o keycodes.o keytypes.o
compat.o action.o symbols.o geometry.o xkbpath.o listing.o
xkbparse.o parseutils.o utils.o -lxkbfile -lXext -lX11
-Wl,-rpath-
daniels@
It's been a while since I've filed a gcc bug, so please let me know what sort of
debug output I need to give you.
Also occurs (100% reproducibly) on xc/programs/ xtrap/xtrapstat s.c.
I'm running on an AthlonXP 2400+ (standard clockspeed, well-cooled, all that),
good Kingston RAM that checked out fine with memtest86. The only real
derivation is that I'm running a self-compiled 2.6.9-rc1-mm1, as I need proper
XFS support, and 2.6.7 hung with my media reader plugged into the USB port (will
check if this still occurs with 2.6.8.1); however, I wouldn't believe this would
affect anything, as it only affects the very same specific files (static across
many unpacks from different .orig tarballs -- initially I thought it was my bad,
deleted the orig, and downloaded it again).