From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH/RFC] overflow and register size mismatch in sh4-softmmu
Date: Sun, 11 Nov 2007 13:33:41 +0000 [thread overview]
Message-ID: <200711111333.42628.paul@codesourcery.com> (raw)
In-Reply-To: <20071111131113.GC25322@tapir>
On Sunday 11 November 2007, Carlo Marcelo Arenas Belon wrote:
> as shown by the following warning when compiling HEAD :
>
> qemu/target-sh4/translate.c: In function `cpu_sh4_reset':
> qemu/target-sh4/translate.c:139: warning: overflow in implicit constant
> conversion
>...
> the following patch changes the logic to use a helper function
> - env->fp_status.float_rounding_mode = float_round_to_zero;
> + set_float_rounding_mode(float_round_to_zero, &env->fp_status);
This is just hiding the bug.
Paul
prev parent reply other threads:[~2007-11-11 13:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-11 13:11 [Qemu-devel] [PATCH/RFC] overflow and register size mismatch in sh4-softmmu Carlo Marcelo Arenas Belon
2007-11-11 13:33 ` Paul Brook [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=200711111333.42628.paul@codesourcery.com \
--to=paul@codesourcery.com \
--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).