From: Peter Maydell <peter.maydell@linaro.org>
To: G 3 <programmingkidx@gmail.com>
Cc: qemu-devel qemu-devel <qemu-devel@nongnu.org>,
"patches@linaro.org" <patches@linaro.org>,
Roman Bolshakov <r.bolshakv@yadro.com>,
BALATON Zoltan <balaton@eik.bme.hu>,
Berkus Decker <berkus@gmail.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Ben Hekster <ben.hekster@foghorn.io>
Subject: Re: [Qemu-devel] [PATCH v3 1/7] ui/cocoa: Ensure we have the iothread lock when calling into QEMU
Date: Fri, 1 Mar 2019 09:47:09 +0000 [thread overview]
Message-ID: <CAFEAcA_uKj+DTxtTcmFyO+OFibxTFccFBfSbZAAZDL2aGH9-Pg@mail.gmail.com> (raw)
In-Reply-To: <CAKyx-3PZyhNN64O2MQP20MT6Xv2A3yLUsTCD6D08s+NtWMeTXg@mail.gmail.com>
On Thu, 28 Feb 2019 at 21:53, G 3 <programmingkidx@gmail.com> wrote:
> On Mon, Feb 25, 2019 at 5:24 AM Peter Maydell <peter.maydell@linaro.org> wrote:
>> +// Utility function to run specified code block with iothread lock held
>> +typedef void (^CodeBlock)(void);
>
>
> Please don't use blocks. It would lock Mac OS X users into having to use CLang. GCC does not support this non-standard extension.
>
> C function pointers and Objective-C's selectors could work in place of blocks.
Clang is the standard toolchain for this OS. We have such
little developer resource for OSX that I don't think we
can reasonably support two toolchains here. Besides,
we need blocks to use dispatch_async(), which is a much
simpler way to achieve what we're trying to do than
the 10.6 compatible approach.
Similarly, I am not prepared to continue to support 10.6
at this point:
* 10.6's last release was over seven years ago
* Apple stopped supporting it four years ago
* there have been multiple OSX releases since then
* attempting to maintain support for 10.6 would make the
code less readable and maintainable for newer OSes
we do care about
* we do not have either the user base or the developer
base on OSX to justify maintaining support for this
ancient OS version
* it would be out of line with our overall host OS
support policy, which targets only the last LTS
version or two of distros and OSes
I'm sorry if this is inconvenient to you personally, but
I don't think it makes any sense as a project to try to
support this any longer.
thanks
-- PMM
next prev parent reply other threads:[~2019-03-01 9:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 10:24 [Qemu-devel] [PATCH v3 0/7] ui/cocoa: Use OSX's main loop Peter Maydell
2019-02-25 10:24 ` [Qemu-devel] [PATCH v3 1/7] ui/cocoa: Ensure we have the iothread lock when calling into QEMU Peter Maydell
2019-02-28 21:53 ` G 3
2019-03-01 9:47 ` Peter Maydell [this message]
2019-02-25 10:24 ` [Qemu-devel] [PATCH v3 2/7] ui/cocoa: Use the pixman image directly in switchSurface Peter Maydell
2019-02-25 10:24 ` [Qemu-devel] [PATCH v3 3/7] ui/cocoa: Factor out initial menu creation Peter Maydell
2019-02-25 10:24 ` [Qemu-devel] [PATCH v3 4/7] ui/cocoa: Move console/device menu creation code up in file Peter Maydell
2019-02-25 10:24 ` [Qemu-devel] [PATCH v3 5/7] ui/cocoa: Don't call NSApp sendEvent directly from handleEvent Peter Maydell
2019-02-25 10:24 ` [Qemu-devel] [PATCH v3 6/7] ui/cocoa: Subclass NSApplication so we can implement sendEvent Peter Maydell
2019-02-25 10:24 ` [Qemu-devel] [PATCH v3 7/7] ui/cocoa: Perform UI operations only on the main thread Peter Maydell
2019-02-28 22:35 ` G 3
2019-02-25 10:28 ` [Qemu-devel] [PATCH v3 0/7] ui/cocoa: Use OSX's main loop Peter Maydell
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_uKj+DTxtTcmFyO+OFibxTFccFBfSbZAAZDL2aGH9-Pg@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=balaton@eik.bme.hu \
--cc=ben.hekster@foghorn.io \
--cc=berkus@gmail.com \
--cc=kraxel@redhat.com \
--cc=patches@linaro.org \
--cc=programmingkidx@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=r.bolshakv@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).