This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Athlon XP segfaults with -fweb -ftracer
- From: Ian Lance Taylor <iant at google dot com>
- To: Daniel Kasak <daniel dot kasak at 247realmedia dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Tue, 02 Dec 2008 07:38:47 -0800
- Subject: Re: Athlon XP segfaults with -fweb -ftracer
- References: <1228173607.6999.11.camel@dkasak>
Daniel Kasak <daniel.kasak@247realmedia.com> writes:
> 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.
Your message should probably have been sent to gcc-help@gcc.gnu.org
rather than to gcc@gcc.gnu.org.
You may or may not have found a bug in the compiler. It's fairly
common for incorrect code to work as expected with some set of options
and fail with a different set of options. However, since you are
using uncommon options, it could certainly be a compiler bug.
Filing a bug report could be helpful, but in order for us to do
anything with it you will need to provide quite a bit more
information. For the kind of information we need, please see
http://gcc.gnu.org/bugs.html . Thanks.
Ian