This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: C optimizer bug
- From: Eric Botcazou <ebotcazou at libertysurf dot fr>
- To: Russell Shaw <rjshaw at iprimus dot com dot au>
- Cc: gcc at gcc dot gnu dot org
- Date: Thu, 6 Mar 2003 10:53:07 +0100
- Subject: Re: C optimizer bug
- References: <3E66EB6D.5000308@iprimus.com.au>
> It's in a GPL project that i've tried narrowing down by commenting out
> various headers, but i can't make a simple example because all the
> compilation and linking is done with a ton of autoconf stuff.
Unfortunately the issue can't be really investigated without a self-contained
testcase. See http://gcc.gnu.org/bugs.html for the procedure.
> How hard is it to find a bug like this by using gdb on gcc-3.2.2 ?
> I've compiled gcc-3.2.2 from source. I know how compilers work (mostly),
> but haven't poked around in gcc.
It's not very easy if you don't already know the GCC internals. The first
thing to do is to read the gccint manual in the doc directory.
--
Eric Botcazou