From: Filip Navara <xnavara@volny.cz>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Win32 build
Date: Tue, 11 Jan 2005 00:56:04 +0100 [thread overview]
Message-ID: <41E31614.7040702@volny.cz> (raw)
In-Reply-To: <41E308AF.908@bellard.org>
Fabrice Bellard wrote:
> Filip Navara wrote:
>
>> Index: target-i386/ops_template.h
>> ===================================================================
>> RCS file: /cvsroot/qemu/qemu/target-i386/ops_template.h,v
>> retrieving revision 1.8
>> diff -u -r1.8 ops_template.h
>> --- target-i386/ops_template.h 3 Jan 2005 23:50:08 -0000 1.8
>> +++ target-i386/ops_template.h 9 Jan 2005 02:18:37 -0000
>> @@ -46,7 +46,7 @@
>> #define SUFFIX q
>> #define DATA_TYPE uint64_t
>> #define DATA_STYPE int64_t
>> -#define DATA_MASK 0xffffffffffffffff
>> +#define DATA_MASK 0xffffffffffffffffULL
>> #else
>> #error unhandled operand size
>> #endif
>
>
> Is this really needed to compile ?
GCC reports lots of warnings like these otherwise:
qemu/target-i386/ops_template.h: In function `compute_all_incq':
qemu/target-i386/ops_template.h:182: warning: integer constant is too
large for "long" type
In file included from e:/DIFFs/qemu/target-i386/op.c:733:
qemu/target-i386/ops_template.h: In function `compute_all_decq':
qemu/target-i386/ops_template.h:204: warning: integer constant is too
large for "long" type
In file included from e:/DIFFs/qemu/target-i386/op.c:733:
qemu/target-i386/ops_template.h: In function `op_shrq_T0_T1':
qemu/target-i386/ops_template.h:436: warning: integer constant is too
large for "long" type
- Filip
prev parent reply other threads:[~2005-01-11 0:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-09 2:25 [Qemu-devel] [PATCH] Win32 build Filip Navara
2005-01-10 16:29 ` [Qemu-devel] " Ronald
2005-01-10 22:58 ` [Qemu-devel] " Fabrice Bellard
2005-01-10 23:56 ` Filip Navara [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=41E31614.7040702@volny.cz \
--to=xnavara@volny.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.