From: Blue Swirl <blauwirbel@gmail.com>
To: Stefan Weil <weil@mail.berlios.de>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] target-sparc: Fix wrong printf argument
Date: Wed, 12 May 2010 22:22:47 +0300 [thread overview]
Message-ID: <AANLkTikS96TA61TYhog49XslA9BWuIJUdvZ1HLscc2Jh@mail.gmail.com> (raw)
In-Reply-To: <1273689279-9297-1-git-send-email-weil@mail.berlios.de>
Thanks, applied.
Another solution would have been to change the return value to uint32_t.
On 5/12/10, Stefan Weil <weil@mail.berlios.de> wrote:
> cpu_get_ccr() returns a target_ulong, so a type cast is needed to avoid
> wrong output on big endian hosts. We could also use TARGET_FMT_lx,
> but that would print 8 instead of 2 digits.
>
> Cc: Blue Swirl <blauwirbel@gmail.com>
> Signed-off-by: Stefan Weil <weil@mail.berlios.de>
> ---
> target-sparc/helper.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/target-sparc/helper.c b/target-sparc/helper.c
> index 4642122..582de10 100644
> --- a/target-sparc/helper.c
> +++ b/target-sparc/helper.c
> @@ -1490,7 +1490,7 @@ void cpu_dump_state(CPUState *env, FILE *f,
> }
> #ifdef TARGET_SPARC64
> cpu_fprintf(f, "pstate: %08x ccr: %02x (icc: ", env->pstate,
> - cpu_get_ccr(env));
> + (unsigned)cpu_get_ccr(env));
> cpu_print_cc(f, cpu_fprintf, cpu_get_ccr(env) << PSR_CARRY_SHIFT);
> cpu_fprintf(f, " xcc: ");
> cpu_print_cc(f, cpu_fprintf, cpu_get_ccr(env) << (PSR_CARRY_SHIFT - 4));
>
> --
> 1.7.1
>
>
prev parent reply other threads:[~2010-05-12 19:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 18:34 [Qemu-devel] [PATCH] target-sparc: Fix wrong printf argument Stefan Weil
2010-05-12 19:22 ` Blue Swirl [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=AANLkTikS96TA61TYhog49XslA9BWuIJUdvZ1HLscc2Jh@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=weil@mail.berlios.de \
/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).