public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/8092: cross-jump triggers too often Date: Tue, 01 Oct 2002 11:56:00 -0000 [thread overview] Message-ID: <20021001185600.5981.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/8092; it has been noted by GNATS. From: Richard Henderson <rth@redhat.com> To: Bernd Paysan <bernd.paysan@gmx.de> Cc: rth@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: optimization/8092: cross-jump triggers too often Date: Tue, 1 Oct 2002 11:55:02 -0700 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~
next reply other threads:[~2002-10-01 18:56 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-01 11:56 Richard Henderson [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-26 18:06 Jorge Acereda Maciá 2003-02-23 21:10 neroden 2002-10-07 4:26 Bernd Paysan 2002-10-06 15:26 Daniel Berlin 2002-10-06 12:46 Bernd Paysan 2002-10-05 14:36 Bernd Paysan 2002-10-05 3:06 Anton Ertl 2002-10-03 16:16 Bernd Paysan 2002-10-01 7:46 Bernd Paysan 2002-09-30 14:20 rth
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20021001185600.5981.qmail@sources.redhat.com \ --to=rth@redhat.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).