From: Carlo Marcelo Arenas Belon <carenas@sajinet.com.pe>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu target-alpha/op_helper.c target-arm/op_hel...
Date: Sun, 11 Nov 2007 08:10:25 -0600 [thread overview]
Message-ID: <20071111141025.GD25322@tapir> (raw)
In-Reply-To: <E1IrC2d-0005MZ-D9@cvs.savannah.gnu.org>
On Sun, Nov 11, 2007 at 12:35:55PM +0000, Fabrice Bellard wrote:
> Modified files:
> target-alpha : op_helper.c
> target-arm : op_helper.c
> target-cris : op_helper.c
> target-m68k : op_helper.c
> target-ppc : op_helper.c
>
> Log message:
> fixed invalid type
why was target_phys_addr_t and invalid type for the program counter? or you
mean that it is better to cast it to unsigned long so that you can never
overflow the pointer and so using unsigned long was better?
Carlo
next prev parent reply other threads:[~2007-11-11 14:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-11 12:35 [Qemu-devel] qemu target-alpha/op_helper.c target-arm/op_hel Fabrice Bellard
2007-11-11 14:10 ` Carlo Marcelo Arenas Belon [this message]
2007-11-11 14:26 ` andrzej zaborowski
-- strict thread matches above, loose matches on Subject: below --
2007-10-29 14:39 Thiemo Seufer
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=20071111141025.GD25322@tapir \
--to=carenas@sajinet.com.pe \
--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).