From: Jose Ricardo Ziviani <joserz@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, nikunj@linux.vnet.ibm.com
Subject: [Qemu-devel] [PATCH Risu 5/5] risugen_ppc64: Remove unused code
Date: Mon, 27 Feb 2017 16:41:32 -0300 [thread overview]
Message-ID: <1488224492-20316-6-git-send-email-joserz@linux.vnet.ibm.com> (raw)
In-Reply-To: <1488224492-20316-1-git-send-email-joserz@linux.vnet.ibm.com>
Because we don't support custom fpsrc value yet it's better to remove
that code.
Signed-off-by: Jose Ricardo Ziviani <joserz@linux.vnet.ibm.com>
---
risugen_ppc64.pm | 4 ----
1 file changed, 4 deletions(-)
diff --git a/risugen_ppc64.pm b/risugen_ppc64.pm
index 46ab7b1..4f7c709 100644
--- a/risugen_ppc64.pm
+++ b/risugen_ppc64.pm
@@ -404,10 +404,6 @@ sub write_test_code($)
print "Generating code using patterns: @keys...\n";
progress_start(78, $numinsns);
- #if ($fp_enabled) {
- # write_set_fpscr($fpscr);
- #}
-
if (grep { defined($insn_details{$_}->{blocks}->{"memory"}) } @keys) {
write_memblock_setup();
}
--
2.7.4
prev parent reply other threads:[~2017-02-27 19:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 19:41 [Qemu-devel] [PATCH Risu 0/5] PPC64 Improvements Jose Ricardo Ziviani
2017-02-27 19:41 ` [Qemu-devel] [PATCH Risu 1/5] risugen_ppc64: Load random 128-bit data to VSX registers Jose Ricardo Ziviani
2017-02-28 5:15 ` Nikunj A Dadhania
2017-02-27 19:41 ` [Qemu-devel] [PATCH Risu 2/5] risu_reginfo_ppc64le: Remove unused code from PPC64 register comparison Jose Ricardo Ziviani
2017-02-28 13:43 ` Peter Maydell
2017-02-28 14:29 ` joserz
2017-02-28 18:01 ` Peter Maydell
2017-02-27 19:41 ` [Qemu-devel] [PATCH Risu 3/5] configure: Add initial support to PPC64 (big endian) Jose Ricardo Ziviani
2017-02-27 19:41 ` [Qemu-devel] [PATCH Risu 4/5] risugen, risugen_ppc64.pm: Add support ppc64 (big-endian) Jose Ricardo Ziviani
2017-02-27 19:41 ` Jose Ricardo Ziviani [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=1488224492-20316-6-git-send-email-joserz@linux.vnet.ibm.com \
--to=joserz@linux.vnet.ibm.com \
--cc=nikunj@linux.vnet.ibm.com \
--cc=peter.maydell@linaro.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).