Athlon XP segfaults with -fweb -ftracer

[Daniel Kasak <daniel dot kasak at 247realmedia dot com>]

Hi all.

I'm a Gentoo user with an Athlon XP:

dkasak@dkasak ~ $ cat /proc/cpuinfo 
processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 6
model           : 10
model name      : AMD Athlon(tm) XP  3000+
stepping        : 0
cpu MHz         : 2157.092
cache size      : 512 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow up
bogomips        : 4314.18
clflush size    : 32
power management: ts

dkasak@dkasak ~ $

I'm using gcc 4.3.2:

dkasak@dkasak ~ $ gcc --version
gcc (Gentoo 4.3.2 p1.1) 4.3.2
Copyright (C) 2008 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is
NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.

dkasak@dkasak ~ $

I'm experiencing segfaults with applications that use fontconfig, only
if fontconfig is compiled with -fweb -ftracer. In full, I used:

-march=athlon-xp -O2 -pipe -fweb -ftracer

I have seen a very similar bugs reported at:

https://bugs.gentoo.org/show_bug.cgi?id=147290
https://bugs.gentoo.org/show_bug.cgi?id=135632

 ... but they talk about -ftree-vectorize. The symptoms are the same
anyway.

If I rebuild fontconfig with:

-march=athlon-xp -O2 -pipe

 ... the segfaults are fixed.

Comment #8 in https://bugs.gentoo.org/show_bug.cgi?id=135632 says that
this is fixed in gcc-4.3, but possibly this was not fixed for athlon-xp?

I can enter a bug with the above info if people want. Should I? Is there
an existing bug / is it still a known issue? I can also rebuild with
debugging symbols if it will help.

Thanks.

Dan