qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "andrzej zaborowski" <balrog@zabor.org>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: strange crash on FreeBSD-current/amd64 (pointer truncation?)
Date: Fri, 2 Feb 2007 23:57:36 +0100	[thread overview]
Message-ID: <fb249edb0702021457h48d69f72n1ab5c22567afea16@mail.gmail.com> (raw)
In-Reply-To: <200702022240.22482.paul@codesourcery.com>

On 02/02/07, Paul Brook <paul@codesourcery.com> wrote:
> > > Isn't that 32 bit for 32 bit targets?  Then it wouldn't fix the bug,
> >
> > Well, it just happens that target_ulong is 64 bit even for 32 bit
> > target on a 64 bit host (as a workaround for something I think, was
> > wondering about it too. I asked on IRC once but no one knew the actual
> > reason). This however doesn't change the fact that target_ulong
> > shouldn't be used here.
>
> Are you sure you're not confusing it with target_phys_address_t?

Oops, right, TARGET_PHYS_ADDR_BITS and TARGET_LONG_BITS are different.
Sorry for the confusion.

Regards,
Andrew

      reply	other threads:[~2007-02-02 22:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-24 20:00 [Qemu-devel] strange crash on FreeBSD-current/amd64 (pointer truncation?) Juergen Lock
2007-02-01 20:00 ` [Qemu-devel] " Juergen Lock
2007-02-02  4:02   ` Thiemo Seufer
2007-02-02 21:45     ` Juergen Lock
2007-02-02 22:24       ` Thiemo Seufer
2007-02-03  1:43         ` Juergen Lock
2007-02-03 18:12           ` Gwenole Beauchesne
2007-02-04 13:38             ` Paul Brook
2007-02-02 22:27       ` andrzej zaborowski
2007-02-02 22:40         ` Paul Brook
2007-02-02 22:57           ` andrzej zaborowski [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=fb249edb0702021457h48d69f72n1ab5c22567afea16@mail.gmail.com \
    --to=balrog@zabor.org \
    --cc=balrogg@gmail.com \
    --cc=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).