From: Akihiko Odaki <akihiko.odaki@gmail.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Roman Bolshakov <r.bolshakov@yadro.com>,
Christian Schoenebeck <qemu_oss@crudebyte.com>,
qemu Developers <qemu-devel@nongnu.org>
Subject: Re: [RFC PATCH 0/4] buildsys: More fixes to use GCC on macOS
Date: Tue, 15 Feb 2022 22:06:41 +0900 [thread overview]
Message-ID: <CAMVc7JU3sd+h4A2R2-hScyLBJyo9Zb8SzLFapMsRdSwJ3KX_xw@mail.gmail.com> (raw)
In-Reply-To: <20220215120625.64711-1-f4bug@amsat.org>
On Tue, Feb 15, 2022 at 9:06 PM Philippe Mathieu-Daudé <f4bug@amsat.org> wrote:
>
> Few fixes to be able to use GCC extensions which are not
> available on Clang.
>
> Philippe Mathieu-Daudé (4):
> osdep: Avoid using Clang-specific __builtin_available()
> osdep: Un-inline qemu_thread_jit_execute/write
> audio: Rename coreaudio extension to use Objective-C compiler
> ui/cocoa: Ignore 'initializer overrides' warnings
>
> audio/{coreaudio.c => coreaudio.m} | 0
> audio/meson.build | 2 +-
> include/qemu/osdep.h | 21 ++-------------------
> ui/cocoa.m | 5 +++++
> util/osdep.c | 20 ++++++++++++++++++++
> 5 files changed, 28 insertions(+), 20 deletions(-)
> rename audio/{coreaudio.c => coreaudio.m} (100%)
>
> --
> 2.34.1
>
Compiler portability is always nice to have. Making QEMU on macOS
compatible with GCC is good, but I don't think that would justify
abandoning compatibility with Clang.
Regards,
Akihiko Odaki
next prev parent reply other threads:[~2022-02-15 13:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 12:06 [RFC PATCH 0/4] buildsys: More fixes to use GCC on macOS Philippe Mathieu-Daudé via
2022-02-15 12:06 ` [RFC PATCH 1/4] osdep: Avoid using Clang-specific __builtin_available() Philippe Mathieu-Daudé via
2022-02-15 12:06 ` [PATCH 2/4] osdep: Un-inline qemu_thread_jit_execute/write Philippe Mathieu-Daudé via
2022-02-15 13:09 ` Akihiko Odaki
2022-02-15 13:29 ` Philippe Mathieu-Daudé via
2022-02-15 12:06 ` [RFC PATCH 3/4] audio: Rename coreaudio extension to use Objective-C compiler Philippe Mathieu-Daudé via
2022-02-15 13:37 ` Christian Schoenebeck
2022-02-15 12:06 ` [RFC PATCH 4/4] ui/cocoa: Ignore 'initializer overrides' warnings Philippe Mathieu-Daudé via
2022-02-15 12:34 ` Peter Maydell
2022-02-15 13:19 ` Akihiko Odaki
2022-02-15 13:23 ` Philippe Mathieu-Daudé via
2022-02-15 13:18 ` Christian Schoenebeck
2022-02-15 13:45 ` Peter Maydell
2022-02-15 14:06 ` Philippe Mathieu-Daudé via
2022-02-15 14:11 ` Christian Schoenebeck
2022-02-15 14:17 ` Peter Maydell
2022-02-15 13:06 ` Akihiko Odaki [this message]
2022-02-15 13:25 ` [RFC PATCH 0/4] buildsys: More fixes to use GCC on macOS Philippe Mathieu-Daudé via
2022-02-16 2:28 ` Akihiko Odaki
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=CAMVc7JU3sd+h4A2R2-hScyLBJyo9Zb8SzLFapMsRdSwJ3KX_xw@mail.gmail.com \
--to=akihiko.odaki@gmail.com \
--cc=f4bug@amsat.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu_oss@crudebyte.com \
--cc=r.bolshakov@yadro.com \
/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).