This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: Possible optimizer bug on sparc-solaris?
- From: Warren_Baird at cimmetry dot com
- To: "Eric Botcazou" <ebotcazou at libertysurf dot fr>
- Cc: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 30 Jul 2003 14:45:52 -0400
- Subject: Re: Possible optimizer bug on sparc-solaris?
Hi Eric,
thanks for your response...
> No, this would be a sheer waste of time. We really need a (small if
> possible) self-contained testcase in order to debug the compiler.
I figured that... Unfortunately it seems to be really dependant on memory
layout... Adding a printf anywhere in the function moves the assignment to %o7,
as did many other small changes I made while trying to track the bug down - it's
probably going to be really hard to build a self-contained test-case... I'm
afraid that I won't even have time to try and build a test-case for a couple of
weeks at least...
> > Is there perhaps a way to tell the optimizer to just ignore register
> > %o7 when optimizing? It might hurt performance a little, but if it
> > avoids crashes like this it might be worth it to us.
>
> It would be better to pinpoint and fix the real bug.
I agree whole-heartedly... Unfortunately we're stabilizing our code for a
release right now, and I'm worried that there may be other places in our code
where this is happening... I could back off to -O1 for the entire code base,
but I'd rather not do that. Is there I way we can disable %o7 until was have a
proper fix for the bug?
Thanks,
Warren