From: Aleksandar Markovic <aleksandar.markovic@rt-rk.com>
To: qemu-devel@nongnu.org
Cc: aurelien@aurel32.net, amarkovic@wavecomp.com, smarkovic@wavecomp.com
Subject: [Qemu-devel] [PATCH v4 00/11] disas: nanoMIPS: Clean up several issues
Date: Mon, 24 Dec 2018 18:19:25 +0100 [thread overview]
Message-ID: <1545671976-13630-1-git-send-email-aleksandar.markovic@rt-rk.com> (raw)
From: Aleksandar Markovic <amarkovic@wavecomp.com>
Clean up several misc issues in nanoMIPS disassembler. There are
more issues to be cleaned, and this is meant to be just the first
phase. Complete cleanup should happen over the course of next
few months.
All these changes should not and do not affect any functionality.
v3->v4:
- added patch "Name more functions in a more descriptive way"
- added patch "Fix order of more invocations"
- added patch "Fix comments for 48-bit instructions"
- minor cleanups of previous commit messages
v2->v3:
- added three patches that fix function misnomers.
- minor changes in commit messages.
v1->v2:
- patch 5 was somehow lost in v1, now should be fine.
Aleksandar Markovic (11):
disas: nanoMIPS: Fix preamble text in nanomips.* files
disas: nanoMIPS: Remove functions that are not used
disas: nanoMIPS: Fix a function misnomer
disas: nanoMIPS: Fix order of some invocations
disas: nanoMIPS: Name some functions in a more descriptive way
disas: nanoMIPS: Fix an FP-related misnomer 1
disas: nanoMIPS: Fix an FP-related misnomer 2
disas: nanoMIPS: Fix an FP-related misnomer 3
disas: nanoMIPS: Name more functions in a more descriptive way
disas: nanoMIPS: Fix order of more invocations
disas: nanoMIPS: Fix comments for 48-bit instructions
disas/nanomips.cpp | 1825 +++++++++++++++++++++++-----------------------------
disas/nanomips.h | 100 ++-
2 files changed, 848 insertions(+), 1077 deletions(-)
--
2.7.4
next reply other threads:[~2018-12-24 17:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-24 17:19 Aleksandar Markovic [this message]
2018-12-24 17:19 ` [Qemu-devel] [PATCH v4 01/11] disas: nanoMIPS: Fix preamble text in nanomips.* files Aleksandar Markovic
2018-12-24 17:19 ` [Qemu-devel] [PATCH v4 02/11] disas: nanoMIPS: Remove functions that are not used Aleksandar Markovic
2018-12-24 17:19 ` [Qemu-devel] [PATCH v4 03/11] disas: nanoMIPS: Fix a function misnomer Aleksandar Markovic
2018-12-24 17:19 ` [Qemu-devel] [PATCH v4 04/11] disas: nanoMIPS: Fix order of some invocations Aleksandar Markovic
2018-12-24 17:19 ` [Qemu-devel] [PATCH v4 05/11] disas: nanoMIPS: Name some functions in a more descriptive way Aleksandar Markovic
2018-12-24 17:19 ` [Qemu-devel] [PATCH v4 06/11] disas: nanoMIPS: Fix an FP-related misnomer 1 Aleksandar Markovic
2018-12-24 17:19 ` [Qemu-devel] [PATCH v4 07/11] disas: nanoMIPS: Fix an FP-related misnomer 2 Aleksandar Markovic
2018-12-24 17:19 ` [Qemu-devel] [PATCH v4 08/11] disas: nanoMIPS: Fix an FP-related misnomer 3 Aleksandar Markovic
2018-12-24 17:19 ` [Qemu-devel] [PATCH v4 09/11] disas: nanoMIPS: Name more functions in a more descriptive way Aleksandar Markovic
2018-12-24 17:19 ` [Qemu-devel] [PATCH v4 10/11] disas: nanoMIPS: Fix order of more invocations Aleksandar Markovic
2018-12-24 17:19 ` [Qemu-devel] [PATCH v4 11/11] disas: nanoMIPS: Fix comments for 48-bit instructions Aleksandar Markovic
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=1545671976-13630-1-git-send-email-aleksandar.markovic@rt-rk.com \
--to=aleksandar.markovic@rt-rk.com \
--cc=amarkovic@wavecomp.com \
--cc=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.org \
--cc=smarkovic@wavecomp.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.