From: Peter Maydell <peter.maydell@linaro.org>
To: Kevin Wolf <kwolf@redhat.com>
Cc: blauwirbel@gmail.com, blueswirl@gmail.com,
Andreas Schwab <schwab@linux-m68k.org>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/5] Avoid GCC extension ?:
Date: Wed, 11 Jul 2012 14:09:53 +0100 [thread overview]
Message-ID: <CAFEAcA_a2-G23N+1xL62DTrKrSpQoG2PrFh7RhDmb7KbDSDaFQ@mail.gmail.com> (raw)
In-Reply-To: <4FFD7790.20201@redhat.com>
On 11 July 2012 13:54, Kevin Wolf <kwolf@redhat.com> wrote:
> Does this patch improve anything? Last time I checked, qemu only
> compiled on gcc anyway.
It would be nice to be able to compile with LLVM/Clang; however
since Clang supports the ?: gcc extension this patch doesn't
move us any further in that direction.
-- PMM
next prev parent reply other threads:[~2012-07-11 13:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-08 11:51 [Qemu-devel] [PATCH 0/5] portability patches blauwirbel
2012-07-08 11:51 ` [Qemu-devel] [PATCH 1/5] Avoid GCC extension ?: blauwirbel
2012-07-08 12:09 ` Andreas Schwab
2012-07-08 12:14 ` Blue Swirl
2012-07-11 12:54 ` Kevin Wolf
2012-07-11 13:09 ` Peter Maydell [this message]
2012-07-11 13:12 ` 陳韋任 (Wei-Ren Chen)
2012-07-12 20:34 ` Blue Swirl
2012-07-12 20:28 ` Blue Swirl
2012-07-12 21:08 ` Peter Maydell
2012-07-13 14:47 ` Blue Swirl
2012-07-13 9:05 ` Kevin Wolf
2012-07-13 14:58 ` Blue Swirl
2012-07-09 7:35 ` Markus Armbruster
2012-07-10 19:09 ` Blue Swirl
2012-07-08 11:51 ` [Qemu-devel] [PATCH 2/5] Avoid returning void blauwirbel
2012-07-08 11:51 ` [Qemu-devel] [PATCH 3/5] Use __asm__ instead of asm or __asm blauwirbel
2012-07-08 11:51 ` [Qemu-devel] [PATCH 4/5] Avoid unportable %m format blauwirbel
2012-07-10 20:53 ` Anthony Liguori
2012-07-10 21:12 ` Stefan Weil
2012-07-10 21:23 ` Anthony Liguori
2012-07-12 19:43 ` Blue Swirl
2012-07-08 11:51 ` [Qemu-devel] [PATCH 5/5] Avoid redefining inline blauwirbel
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=CAFEAcA_a2-G23N+1xL62DTrKrSpQoG2PrFh7RhDmb7KbDSDaFQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=blauwirbel@gmail.com \
--cc=blueswirl@gmail.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=schwab@linux-m68k.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).