qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Desnogues <laurent.desnogues@gmail.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] User mode issue for loading 32-bit ELF on 64-bit guest processor
Date: Wed, 21 Jan 2009 08:06:42 +0100	[thread overview]
Message-ID: <761ea48b0901202306v17231be3r609a873d87e1cae4@mail.gmail.com> (raw)
In-Reply-To: <200901210540.58796.paul@codesourcery.com>

On Wed, Jan 21, 2009 at 6:40 AM, Paul Brook <paul@codesourcery.com> wrote:
>> 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.

Indeed these *_ulong types can be confusing especially in
that case where elfload32.c sets TARGET_ABI32 before
including elfload.c which includes qemu.h and then
qemu-types.h which looks like this:

#ifdef TARGET_ABI32
typedef uint32_t abi_ulong;
#else
typedef target_ulong abi_ulong;
#endif

and then qemu.h defines the structures that cause trouble.


Laurent

      reply	other threads:[~2009-01-21  7:06 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
2009-01-21  7:06   ` Laurent Desnogues [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=761ea48b0901202306v17231be3r609a873d87e1cae4@mail.gmail.com \
    --to=laurent.desnogues@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).