From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Win32 build
Date: Mon, 10 Jan 2005 23:58:55 +0100 [thread overview]
Message-ID: <41E308AF.908@bellard.org> (raw)
In-Reply-To: <41E09627.1020802@volny.cz>
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 ?
Fabrice.
next prev parent reply other threads:[~2005-01-10 23:17 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 ` Fabrice Bellard [this message]
2005-01-10 23:56 ` [Qemu-devel] " Filip Navara
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=41E308AF.908@bellard.org \
--to=fabrice@bellard.org \
--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).