Is this serious? (about amd64 CFLAGS)

Message

tnt · Post by **tnt** » Tue Dec 28, 2004 12:38 am

Dec 23 18:12:46 tux ld[19303]: segfault at 0000000000000020 rip 0000002a9579e915 rsp 0000007fbfffd520 error 4
Dec 24 04:33:59 tux conftest[19352]: segfault at 00000000bfffdf82 rip 0000002a95791ae1 rsp 0000007fbfffde70 error 4
Dec 24 04:34:48 tux conftest[29801]: segfault at ffffffff9588f180 rip 0000002a95b04630 rsp 0000007fbfffde48 error 4
Dec 25 11:49:50 tux cc1[10082]: segfault at 00000000000000e0 rip 00000000000000e0 rsp 0000007fbfffd368 error 14
Dec 27 22:44:09 tux X[5541]: segfault at 0000000000000000 rip 0000000000000000 rsp 0000007fbfffeb08 error 14
Dec 28 01:32:05 tux X[6069]: segfault at 0000000000000000 rip 0000000000000000 rsp 0000007fbfffea28 error 14

It crashes my KDE every few hours.
Is it serious?

robnotts · Post by **robnotts** » Tue Dec 28, 2004 9:01 am

I would say "YES"... I have ran my machine for days on end, running kde without a crash in sight...

Obvious suggestions... start with a full memory check to ensure all is correct in that department... then... any crazy c-flags? any ~amd64 libraries that perhaps should be just plain old amd64 ones?

Rob.

tnt · Post by **tnt** » Wed Dec 29, 2004 1:58 pm

I've had a lot of X restartings (as it's set to restart X server upon crash), and I've even had few hard-locks that I could resolve only be hardware reset.

My memory works fine. It can pass all tests in memtest86+ and prime can be run forever without problems.

I've compiled kde 3.3.2 with (selective) ~amd64 flag and thought that's the problem, but as I can see - the kde 3.3.2 is marked stable for amd64 right now.
Only other things I've compiled with ~amd64 flag were openoffice 1.1.4 and ksensors 0.7.3. As I didn't use openoffice at the time of segfaults I gues that could only be ksensors (that were active as trayicon).
I'll turn off ksensors to see what's happening...

But, I'm afraid it is not the only problem: I've tryed to compile xine-lib and kde in the runlevel "single", so there where no ksensors and anything at all (even network) and I still had some segfaults by gcc.

Maybe there's a problem with my USE and/or CFLAGS flags:

Code: Select all

tux root # emerge info
Portage 2.0.51-r3 (default-linux/amd64/2004.3, gcc-3.4.3, glibc-2.3.4.20040808-r1, 2.6.9-gentoo-r12 x86_64)
=================================================================
System uname: 2.6.9-gentoo-r12 x86_64 AMD Athlon(tm) 64 Processor 3000+
Gentoo Base System version 1.4.16
Autoconf: sys-devel/autoconf-2.59-r5
Automake: sys-devel/automake-1.8.5-r1
Binutils: sys-devel/binutils-2.15.90.0.1.1-r3
Headers:  sys-kernel/linux26-headers-2.6.8.1-r1
Libtools: sys-devel/libtool-1.5.2-r7
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CFLAGS="-march=athlon64 -O3 -pipe -ffast-math -funroll-all-loops -funit-at-a-time -fpeel-loops -ftracer -funswitch-loops  -fomit-frame-pointer -frename-registers -fweb"
CHOST="x86_64-pc-linux-gnu"
COMPILER=""
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=athlon64 -O3 -pipe -ffast-math -funroll-all-loops -funit-at-a-time -fpeel-loops -ftracer -funswitch-loops  -fomit-frame-pointer -frename-registers -fweb -fvisibility-inlines-hidden"
DISTDIR="/storage/backup/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox"
GENTOO_MIRRORS="ftp://mirror.etf.bg.ac.yu/gentoo/ http://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ http://gd.tuwien.ac.at/opsys/linux/gentoo/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="amd64 X aac acpi alsa apache2 arts avi berkdb bitmap-fonts bzlib cdparanoia cdr crypt cups dga divx4linux dvd dvdr encode exif f77 fam flac font-server fortran gcj gd gif gphoto2 gtk2 icq imagemagick imlib innodb ipv6 jabber java jp2 jpeg kde lzw lzw-tiff motif mozilla mpeg multilib mysql nas ncurses nls nptl oggvorbis opengl pam pdflib perl php png python qt quicktime readline real samba slang snmp speexssl tcpd tiff truetype unicode usb userlocales videos xine xml xml2 xmms xpm xrandr xv xvid zlib"

tux root #

Any ideas?

loftwyr · Post by **loftwyr** » Wed Dec 29, 2004 2:41 pm

Yes, get rid of these from your CFLAGS and recompile...

-ffast-math -funroll-all-loops -funit-at-a-time -fpeel-loops -ftracer -funswitch-loops -fweb

Some of these can really destabilize x86_64 builds.

-march=athlon64 -pipe -fomit-frame-pointer -O3 will do as good or better and not leave your system segfaulting.

racoontje · Post by **racoontje** » Wed Dec 29, 2004 3:42 pm

NOFI but read up on optimization flags before you throw stuff at it that of which you don't even know what it does...

-funit-at-a-time is in -O2 and by extention -O3... This shouldn't matter, but as proved by some people in the "AMD recommended CFLAGS" thread, it does.

Anyway your CFLAGS are OTT.

tnt · Post by **tnt** » Wed Dec 29, 2004 4:39 pm

loftwyr wrote:-ffast-math -funroll-all-loops -funit-at-a-time -fpeel-loops -ftracer -funswitch-loops -fweb

Some of these can really destabilize x86_64 builds.

-march=athlon64 -pipe -fomit-frame-pointer -O3 will do as good or better and not leave your system segfaulting.

But, isn't -fweb included in -O3? You said it can destabilize x64_64?
And here
http://forums.gentoo.org/viewtopic.php? ... ght=cflags
I've found that "AMD recomended" flags are:

Code: Select all

CFLAGS="-O3 -march=athlon64 -ffast-math -funroll-all-loops -funit-at-a-time -fpeel-loops -ftracer -funswitch-loops -fomit-frame-pointer -pipe"

Should I leave out -ffasth-math -funroll-all-loops -funit-at-a-time -fpeel-loops -ftracer and -funswitch-loops altought they are recomended by AMD?

racoontje wrote: Anyway your CFLAGS are OTT.

I'm not so good in English. What does "OTT" mean?

ryceck · Post by **ryceck** » Wed Dec 29, 2004 5:32 pm

tnt wrote:
loftwyr wrote:-ffast-math -funroll-all-loops -funit-at-a-time -fpeel-loops -ftracer -funswitch-loops -fweb

Some of these can really destabilize x86_64 builds.

-march=athlon64 -pipe -fomit-frame-pointer -O3 will do as good or better and not leave your system segfaulting.
But, isn't -fweb included in -O3? You said it can destabilize x64_64?
And here
http://forums.gentoo.org/viewtopic.php? ... ght=cflags
I've found that "AMD recomended" flags are:
Code: Select all
CFLAGS="-O3 -march=athlon64 -ffast-math -funroll-all-loops -funit-at-a-time -fpeel-loops -ftracer -funswitch-loops -fomit-frame-pointer -pipe"
Should I leave out -ffasth-math -funroll-all-loops -funit-at-a-time -fpeel-loops -ftracer and -funswitch-loops altought they are recomended by AMD?

racoontje wrote: Anyway your CFLAGS are OTT.
I'm not so good in English. What does "OTT" mean?

U wanna get it stable or what???
Just leave out all the flags except "-O3 -march=athlon64 -pipe" and see if that stabilizes things. If that works reenter ur flags one at a time (or multiple) to locate the problem 100%. Thats the way to pinpoint it

tnt · Post by **tnt** » Wed Dec 29, 2004 5:38 pm

OK. Thanx!

racoontje · Post by **racoontje** » Wed Dec 29, 2004 5:50 pm

tnt wrote:
loftwyr wrote:-ffast-math -funroll-all-loops -funit-at-a-time -fpeel-loops -ftracer -funswitch-loops -fweb

Some of these can really destabilize x86_64 builds.

-march=athlon64 -pipe -fomit-frame-pointer -O3 will do as good or better and not leave your system segfaulting.
But, isn't -fweb included in -O3? You said it can destabilize x64_64?
And here
http://forums.gentoo.org/viewtopic.php? ... ght=cflags
I've found that "AMD recomended" flags are:
Code: Select all
CFLAGS="-O3 -march=athlon64 -ffast-math -funroll-all-loops -funit-at-a-time -fpeel-loops -ftracer -funswitch-loops -fomit-frame-pointer -pipe"
Should I leave out -ffasth-math -funroll-all-loops -funit-at-a-time -fpeel-loops -ftracer and -funswitch-loops altought they are recomended by AMD?

racoontje wrote: Anyway your CFLAGS are OTT.
I'm not so good in English. What does "OTT" mean?

Well, simply put, yes, the CFLAGS aren't perfect.
OTT = over the top