From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [4409] no need to define global registers in cpu-exec.c
Date: Sat, 10 May 2008 11:01:31 +0000 [thread overview]
Message-ID: <E1JumpX-0007Tz-D1@cvs.savannah.gnu.org> (raw)
Revision: 4409
http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=4409
Author: bellard
Date: 2008-05-10 11:01:31 +0000 (Sat, 10 May 2008)
Log Message:
-----------
no need to define global registers in cpu-exec.c
Modified Paths:
--------------
trunk/target-i386/exec.h
Modified: trunk/target-i386/exec.h
===================================================================
--- trunk/target-i386/exec.h 2008-05-10 10:58:20 UTC (rev 4408)
+++ trunk/target-i386/exec.h 2008-05-10 11:01:31 UTC (rev 4409)
@@ -32,6 +32,8 @@
/* at least 4 register variables are defined */
register struct CPUX86State *env asm(AREG0);
+#ifndef CPU_NO_GLOBAL_REGS
+
#if TARGET_LONG_BITS > HOST_LONG_BITS
/* no registers can be used */
@@ -47,49 +49,10 @@
register target_ulong T1 asm(AREG2);
register target_ulong T2 asm(AREG3);
-/* if more registers are available, we define some registers too */
-#ifdef AREG4
-register target_ulong EAX asm(AREG4);
-#define reg_EAX
-#endif
-
-#ifdef AREG5
-register target_ulong ESP asm(AREG5);
-#define reg_ESP
-#endif
-
-#ifdef AREG6
-register target_ulong EBP asm(AREG6);
-#define reg_EBP
-#endif
-
-#ifdef AREG7
-register target_ulong ECX asm(AREG7);
-#define reg_ECX
-#endif
-
-#ifdef AREG8
-register target_ulong EDX asm(AREG8);
-#define reg_EDX
-#endif
-
-#ifdef AREG9
-register target_ulong EBX asm(AREG9);
-#define reg_EBX
-#endif
-
-#ifdef AREG10
-register target_ulong ESI asm(AREG10);
-#define reg_ESI
-#endif
-
-#ifdef AREG11
-register target_ulong EDI asm(AREG11);
-#define reg_EDI
-#endif
-
#endif /* ! (TARGET_LONG_BITS > HOST_LONG_BITS) */
+#endif /* ! CPU_NO_GLOBAL_REGS */
+
#define A0 T2
extern FILE *logfile;
reply other threads:[~2008-05-10 11:01 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=E1JumpX-0007Tz-D1@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).