From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, kwolf@redhat.com, qemu-block@nongnu.org
Subject: [Qemu-devel] [PATCH] build: Work around SIZE_MAX bug in OSX headers
Date: Tue, 12 Jul 2016 09:21:52 -0600 [thread overview]
Message-ID: <1468336912-20396-1-git-send-email-eblake@redhat.com> (raw)
C99 requires SIZE_MAX to be declared with the same type as the
integral promotion of size_t, but OSX mistakenly defines it as
an unsigned long long expression even though size_t is only
unsigned long. Rather than futzing around with whether size_t
is 32- or 64-bits wide, let the compiler get the right type
for us by virtue of integer promotion.
See also https://patchwork.ozlabs.org/patch/542327/ for an
instance where the wrong type trips us up if we don't fix it
for good in osdep.h.
Signed-off-by: Eric Blake <eblake@redhat.com>
---
I can't test this on OSX, but I _did_ test that if I remove the
'#ifdef __APPLE__' conditional (and just blindly do the redefine),
things still compile on Linux (which means I got the type
computation correct).
This is my response to
https://lists.gnu.org/archive/html/qemu-devel/2016-07/msg02276.html
include/qemu/osdep.h | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/include/qemu/osdep.h b/include/qemu/osdep.h
index 7361006..9b4b2d3 100644
--- a/include/qemu/osdep.h
+++ b/include/qemu/osdep.h
@@ -141,6 +141,13 @@ extern int daemon(int, int);
# error Unknown pointer size
#endif
+/* Mac OSX has a <stdint.h> bug that incorrectly defines SIZE_MAX with
+ * the wrong type */
+#ifdef __APPLE__
+#undef SIZE_MAX
+#define SIZE_MAX ((sizeof(char)) * -1)
+#endif
+
#ifndef MIN
#define MIN(a, b) (((a) < (b)) ? (a) : (b))
#endif
--
2.5.5
next reply other threads:[~2016-07-12 15:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 15:21 Eric Blake [this message]
2016-07-12 18:23 ` [Qemu-devel] [PATCH] build: Work around SIZE_MAX bug in OSX headers Eric Blake
2016-07-12 19:35 ` Peter Maydell
2016-07-12 20:22 ` Eric Blake
2016-07-13 7:50 ` Markus Armbruster
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=1468336912-20396-1-git-send-email-eblake@redhat.com \
--to=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.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).