From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [4598] removed unused code
Date: Tue, 27 May 2008 21:18:41 +0000 [thread overview]
Message-ID: <E1K16Z7-0006AT-8t@cvs.savannah.gnu.org> (raw)
Revision: 4598
http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=4598
Author: bellard
Date: 2008-05-27 21:18:39 +0000 (Tue, 27 May 2008)
Log Message:
-----------
removed unused code
Modified Paths:
--------------
trunk/cpu-exec.c
Modified: trunk/cpu-exec.c
===================================================================
--- trunk/cpu-exec.c 2008-05-27 21:15:56 UTC (rev 4597)
+++ trunk/cpu-exec.c 2008-05-27 21:18:39 UTC (rev 4598)
@@ -621,13 +621,6 @@
env->current_tb = NULL;
/* reset soft MMU for next block (it can currently
only be set by a memory fault) */
-#if defined(TARGET_I386) && !defined(CONFIG_SOFTMMU)
- if (env->hflags & HF_SOFTMMU_MASK) {
- env->hflags &= ~HF_SOFTMMU_MASK;
- /* do not allow linking to another block */
- next_tb = 0;
- }
-#endif
#if defined(USE_KQEMU)
#define MIN_CYCLE_BEFORE_SWITCH (100 * 1000)
if (kqemu_is_ok(env) &&
reply other threads:[~2008-05-27 21:18 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=E1K16Z7-0006AT-8t@cvs.savannah.gnu.org \
--to=fabrice@bellard.org \
--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).