qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [RFC PATCH 0/4] buildsys: More fixes to use GCC on macOS


From: Philippe Mathieu-Daudé
Subject: Re: [RFC PATCH 0/4] buildsys: More fixes to use GCC on macOS
Date: Tue, 15 Feb 2022 14:25:08 +0100
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.5.1

On 15/2/22 14:06, Akihiko Odaki wrote:
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.

I am certainly not abandoning compatibility with Clang. What gives
you this impression?



reply via email to

[Prev in Thread] Current Thread [Next in Thread]