qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Weil <weil@mail.berlios.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qtest: fix 32-bit build
Date: Fri, 30 Mar 2012 21:23:05 +0200	[thread overview]
Message-ID: <4F760819.60409@mail.berlios.de> (raw)
In-Reply-To: <4F760697.7060304@codemonkey.ws>

Am 30.03.2012 21:16, schrieb Anthony Liguori:
> On 03/30/2012 02:13 PM, Paolo Bonzini wrote:
>> Il 30/03/2012 21:06, Anthony Liguori ha scritto:
>>> On 03/30/2012 01:55 PM, Paolo Bonzini wrote:
>>>> Il 30/03/2012 20:29, Anthony Liguori ha scritto:
>>>>>> Now it will fail with w64 (which uses 64 bit time_t and
>>>>>> a 32 bit long).
>>>>>
>>>>> That's a bug in w64 (it has a broken ABI).
>>>>>
>>>>> Do we actually build and run on w64??
>>>>
>>>> It's actually sensible and x32 does the same.  Not too urgent though.
>>>
>>> I don't understand how making a long 32 bit is sensible but...  I 
>>> sent a
>>> patch that should at least address q64.
>>>
>>> Am not sure what x32 is though.
>>
>> x32 is 32-bit ABI (with 32-bit pointers and 4GB address space) with the
>> x86-64 (64-bit) ISA.
>
> Wow.  That's..  interesting :-)
>
> In general, violating sizeof(long) >= sizeof(void *) seems like an 
> exceeding bad idea to me.
>
> Regards,
>
> Anthony Liguori

Any 32 bit system will have to use a 64 bit time_t sooner or later
to avoid an overflow. Not only w64 but also w32 supports it.
Future 32 bit Linux versions will also need it.

The size of a long is a different matter.

Regards,
Stefan W.

  reply	other threads:[~2012-03-30 19:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-30 17:54 [Qemu-devel] [PATCH] qtest: fix 32-bit build Anthony Liguori
2012-03-30 17:59 ` Anthony Liguori
2012-03-30 18:03   ` Stefan Weil
2012-03-30 18:29     ` Anthony Liguori
2012-03-30 18:55       ` Paolo Bonzini
2012-03-30 19:06         ` Anthony Liguori
2012-03-30 19:13           ` Paolo Bonzini
2012-03-30 19:16             ` Anthony Liguori
2012-03-30 19:23               ` Stefan Weil [this message]
2012-03-30 19:27                 ` Anthony Liguori
2012-03-30 19:57             ` Blue Swirl
2012-03-30 23:19 ` Eric Blake

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=4F760819.60409@mail.berlios.de \
    --to=weil@mail.berlios.de \
    --cc=anthony@codemonkey.ws \
    --cc=pbonzini@redhat.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).