From: Richard Henderson <rth@twiddle.net>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, schwab@linux-m68k.org,
laurent@vivier.eu, gerg@uclinux.org
Subject: [Qemu-devel] [PATCH 00/11] Proposed format for m68k flags
Date: Fri, 14 Aug 2015 07:59:15 -0700 [thread overview]
Message-ID: <1439564366-11633-1-git-send-email-rth@twiddle.net> (raw)
As promised a couple of days ago, with the addition of CC_OP_CMP,
which wasn't in the text of my proposal the other day. From the
looks of the generated code, I believe this is ideal.
The following is based on Laurent's 8/30 Update cpu flags management.
FWIW, there's something in the last patch here that breaks the
coldfire kernel I've been testing (it may even be a bug in tcg;
the problem only appears well into the boot process). But I'm
about to go away for the weekend and still wanted to include it
to show what can be done.
For convenience, the complete tree pushed to
git://github.com/rth7680/qemu.git tgt-m68k
r~
Richard Henderson (11):
target-m68k: Print flags properly
target-m68k: Some fixes to SR and flags management
target-m68k: Remove incorrect clearing of cc_x
target-m68k: Replace helper_xflag_lt with setcond
target-m68k: Reorg flags handling
target-m68k: Introduce DisasCompare
target-m68k: Use setcond for scc
target-m68k: Optimize some comparisons
target-m68k: Optimize gen_flush_flags
target-m68k: Inline shifts
target-m68k: Inline addx, subx, negx
target-m68k/cpu.c | 2 +-
target-m68k/cpu.h | 48 +--
target-m68k/helper.c | 399 +++++++++----------------
target-m68k/helper.h | 12 +-
target-m68k/op_helper.c | 35 +--
target-m68k/qregs.def | 6 +-
target-m68k/translate.c | 769 +++++++++++++++++++++++++++++++-----------------
7 files changed, 674 insertions(+), 597 deletions(-)
--
2.4.3
next reply other threads:[~2015-08-14 15:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 14:59 Richard Henderson [this message]
2015-08-14 14:59 ` [Qemu-devel] [PATCH 01/11] target-m68k: Print flags properly Richard Henderson
2015-08-14 14:59 ` [Qemu-devel] [PATCH 02/11] target-m68k: Some fixes to SR and flags management Richard Henderson
2015-08-14 14:59 ` [Qemu-devel] [PATCH 03/11] target-m68k: Remove incorrect clearing of cc_x Richard Henderson
2015-08-14 17:04 ` Andreas Schwab
2015-08-14 23:10 ` Richard Henderson
2015-08-15 6:25 ` Andreas Schwab
2015-08-14 14:59 ` [Qemu-devel] [PATCH 04/11] target-m68k: Replace helper_xflag_lt with setcond Richard Henderson
2015-08-14 14:59 ` [Qemu-devel] [PATCH 05/11] target-m68k: Reorg flags handling Richard Henderson
2015-08-14 14:59 ` [Qemu-devel] [PATCH 06/11] target-m68k: Introduce DisasCompare Richard Henderson
2015-08-14 14:59 ` [Qemu-devel] [PATCH 07/11] target-m68k: Use setcond for scc Richard Henderson
2015-08-14 14:59 ` [Qemu-devel] [PATCH 08/11] target-m68k: Optimize some comparisons Richard Henderson
2015-08-14 14:59 ` [Qemu-devel] [PATCH 09/11] target-m68k: Optimize gen_flush_flags Richard Henderson
2015-08-14 14:59 ` [Qemu-devel] [PATCH 10/11] target-m68k: Inline shifts Richard Henderson
2015-08-14 14:59 ` [Qemu-devel] [PATCH 11/11] target-m68k: Inline addx, subx, negx Richard Henderson
2015-08-14 15:37 ` [Qemu-devel] [PATCH 00/11] Proposed format for m68k flags Laurent Vivier
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=1439564366-11633-1-git-send-email-rth@twiddle.net \
--to=rth@twiddle.net \
--cc=gerg@uclinux.org \
--cc=laurent@vivier.eu \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=schwab@linux-m68k.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).