This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: optimization/8092: cross-jump triggers too often
- From: Richard Henderson <rth at redhat dot com>
- To: Bernd Paysan <bernd dot paysan at gmx dot de>
- Cc: rth at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, gcc-gnats at gcc dot gnu dot org
- Date: Tue, 1 Oct 2002 11:55:02 -0700
- Subject: Re: optimization/8092: cross-jump triggers too often
- References: <20020930212033.32125.qmail@sources.redhat.com> <200210011638.40807.bernd.paysan@gmx.de>
On Tue, Oct 01, 2002 at 04:38:40PM +0200, Bernd Paysan wrote:
> Ok, here's engine.i (compressed with bzip2). The relevant function is
> engine.
Well I'm horrified all right -- by the source. For the record, I
wouldn't count on this thing working indefinitely.
I had to modify it a bit to get it to compile with mainline. The
use of asm register variables falls over the compiler's use of
__builtin_memset, which requires edi. I wish I could give a proper
error message for this instead of ICE, but we don't save enough
information long enough for me to remember that this is the user's
fault.
Anyway, I don't see anything that sticks out like a sore thumb wrt
either cross-jumping or gcse. Can you be more specific?
r~