qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: TJ <linux@tjworld.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC] linux-user (mostly syscall.c)
Date: Sat, 03 Nov 2007 17:24:45 +0000	[thread overview]
Message-ID: <1194110685.13889.21.camel@hephaestion> (raw)
In-Reply-To: <1194048343.2168.48.camel@phantasm.home.enterpriseandprosperity.com>

I'm glad you posted about your efforts since I've also been working on
solving related x86_64 build warnings caused by 32-bit int to 64-bit
pointer conversions. 

warning: cast to pointer from integer of different size

There are a lot of these in syscall.c

I have in my drafts folder an RFC I was planning to post detailing the
issue (1,053 warnings in the x64_64 build) and how to resolve them -
some simply require a cast from abi_long/unit32_t to a larger integer
storage (same size as host-pointer-size) using the various pre-processor
macros and typedefs so the compiler can do implicit conversion from the
larger integer type to the pointer.

I'll post what I've written so far so it can be considered in
conjunction with your work.

The title is "RFC: x86_64 Best way to fix 'cast to pointer from integer
of different size' problems?"

TJ.

      parent reply	other threads:[~2007-11-03 17:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-03  0:05 [Qemu-devel] [RFC] linux-user (mostly syscall.c) Thayne Harbaugh
2007-11-03  1:21 ` Thiemo Seufer
2007-11-03 12:52   ` J. Mayer
2007-11-03 14:15     ` Thayne Harbaugh
2007-11-03 19:13       ` Fabrice Bellard
2007-11-04  1:16         ` Thayne Harbaugh
2007-11-04  1:35           ` J. Mayer
2007-11-04  1:51             ` Paul Brook
2007-11-04  7:49               ` J. Mayer
2007-11-03 17:24 ` TJ [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=1194110685.13889.21.camel@hephaestion \
    --to=linux@tjworld.net \
    --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).