From: Richard Henderson <rth@twiddle.net>
To: Gabriel Kerneis <gabriel@kerneis.info>
Cc: qemu-trivial@nongnu.org, Alexander Graf <agraf@suse.de>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] s390x: use CONFIG_INT128 to detect __uint128_t
Date: Tue, 23 Apr 2013 21:37:44 +0100 [thread overview]
Message-ID: <5176F118.6050708@twiddle.net> (raw)
In-Reply-To: <1366737312-8598-1-git-send-email-gabriel@kerneis.info>
On 2013-04-23 18:15, Gabriel Kerneis wrote:
> Target s390x uses ad-hoc macro magic to guess if the compiler
> supports the GCC extension __uint128_t. This patch uses the
> the dedicated macro CONFIG_INT128 defined by configure instead.
>
> This fixes compilation with the CIL source code analyzer, which
> uses GCC as a preprocessor but does not support __uint128_t.
>
> Signed-off-by: Gabriel Kerneis <gabriel@kerneis.info>
Reviewed-by: Richard Henderson <rth@twiddle.net>
r~
next prev parent reply other threads:[~2013-04-23 20:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 17:15 [Qemu-devel] [PATCH] s390x: use CONFIG_INT128 to detect __uint128_t Gabriel Kerneis
2013-04-23 20:37 ` Richard Henderson [this message]
2013-04-26 9:58 ` [Qemu-devel] [Qemu-trivial] " Stefan Hajnoczi
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=5176F118.6050708@twiddle.net \
--to=rth@twiddle.net \
--cc=agraf@suse.de \
--cc=gabriel@kerneis.info \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).