From: Nick Clifton <nickc@redhat.com>
To: Joel Sherrill <joel.sherrill@OARcorp.com>
Cc: gcc@gcc.gnu.org
Subject: Re: mcore-elf on 3.3 branch
Date: Tue, 13 May 2003 18:39:00 -0000 [thread overview]
Message-ID: <m3llxa66lg.fsf@redhat.com> (raw)
In-Reply-To: <3EBFDFB0.72DD73FC@OARcorp.com> (Joel Sherrill's message of "Mon, 12 May 2003 12:53:52 -0500")
Hi Joel,
> mcore-elf has a problem on the 3.3 branch. I currently have a
> cc1 running with over 17 minutes CPU time on a 2.4 Ghz P4
> compiling _lshrdi3.o.
... and here is a proper patch to fix the problem.
A jump insn was being generated by a call to emit_insn() which was
confusing find_basic_blocks(), which then caused the target of the
jump to be deleted (for being in an unreachable block), which then
confused the if-conversion code.
I am going to apply this patch to the mainline sources, but since the
3.3 branch is frozen it will have to wait until after the release.
Cheers
Nick
2003-05-13 Nick Clifton <nickc@redhat.com>
* config/mcore/mcore.md (jump): Use emit_jump_insn.
Index: gcc/config/mcore/mcore.md
===================================================================
RCS file: /cvs/gcc/gcc/gcc/config/mcore/mcore.md,v
retrieving revision 1.9
diff -c -3 -p -w -r1.9 mcore.md
*** gcc/config/mcore/mcore.md 20 Dec 2002 04:30:51 -0000 1.9
--- gcc/config/mcore/mcore.md 13 May 2003 18:34:40 -0000
***************
*** 1896,1902 ****
""
"
{
! emit_insn (gen_jump_real (operand0));
DONE;
}
")
--- 1896,1902 ----
""
"
{
! emit_jump_insn (gen_jump_real (operand0));
DONE;
}
")
prev parent reply other threads:[~2003-05-13 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 18:03 Joel Sherrill
2003-05-13 17:23 ` Nick Clifton
2003-05-13 18:39 ` Nick Clifton [this message]
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=m3llxa66lg.fsf@redhat.com \
--to=nickc@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=joel.sherrill@OARcorp.com \
/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: link
Be 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).