From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Laurent Desnogues <laurent.desnogues@gmail.com>
Subject: Re: [Qemu-devel] User mode issue for loading 32-bit ELF on 64-bit guest processor
Date: Wed, 21 Jan 2009 05:40:58 +0000 [thread overview]
Message-ID: <200901210540.58796.paul@codesourcery.com> (raw)
In-Reply-To: <761ea48b0901201223q628928e7qe586c42e147a7b6c@mail.gmail.com>
> Blue Swirl proposed to use accessors for these structures
> while I proposed to use a new abi_ulong-like type that would
> be the same no matter whether TARGET_ABI32 is defined or
> not. As I am not sure there aren't some other structures that
> would need such a type, I think my proposal is less intrusive.
> The drawback is that it would introduce a new type and we
> already have many such *_ulong types :-)
I'm confused. Isn't this either target_ulong or abi_ulong?
I don't see what other possibilities there are.
Paul
next prev parent reply other threads:[~2009-01-21 5:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 20:23 [Qemu-devel] User mode issue for loading 32-bit ELF on 64-bit guest processor Laurent Desnogues
2009-01-21 5:40 ` Paul Brook [this message]
2009-01-21 7:06 ` Laurent Desnogues
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=200901210540.58796.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=laurent.desnogues@gmail.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).