From: Aurelien Jarno <aurelien@aurel32.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [6938] target-mips: optimize gen_HILO()
Date: Sun, 29 Mar 2009 01:19:13 +0000 [thread overview]
Message-ID: <E1Lnjg9-00086U-A7@cvs.savannah.gnu.org> (raw)
Revision: 6938
http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=6938
Author: aurel32
Date: 2009-03-29 01:19:12 +0000 (Sun, 29 Mar 2009)
Log Message:
-----------
target-mips: optimize gen_HILO()
Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
Modified Paths:
--------------
trunk/target-mips/translate.c
Modified: trunk/target-mips/translate.c
===================================================================
--- trunk/target-mips/translate.c 2009-03-29 01:19:02 UTC (rev 6937)
+++ trunk/target-mips/translate.c 2009-03-29 01:19:12 UTC (rev 6938)
@@ -1795,10 +1795,6 @@
tcg_gen_movi_tl(cpu_LO[0], 0);
opn = "mtlo";
break;
- default:
- MIPS_INVAL(opn);
- generate_exception(ctx, EXCP_RI);
- return;
}
MIPS_DEBUG("%s %s", opn, regnames[reg]);
}
reply other threads:[~2009-03-29 1:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E1Lnjg9-00086U-A7@cvs.savannah.gnu.org \
--to=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.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: 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 NNTP newsgroup(s).