All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Programmingkid <programmingkidx@gmail.com>,
	qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qemu-coroutine.c: error: thread-local storage not supported for this target
Date: Sat, 24 Jan 2015 19:33:15 +0000	[thread overview]
Message-ID: <CAFEAcA8Jo+NPg-GuGi7-fSH9RoGHwKVgA5oq8ogbkzW0t4=c7w@mail.gmail.com> (raw)
In-Reply-To: <54C3EA60.5080801@redhat.com>

On 24 January 2015 at 18:54, Paolo Bonzini <pbonzini@redhat.com> wrote:
> Note that GCC 4.3 was released almost seven years ago; we've been
> requiring it on Windows for three years (commit 00dccaf, coroutine:
> introduce coroutines, 2011-01-17), and no one has ever complained.
>
> Apple is not providing it for Mac OS X 10.6.x only because of political
> reasons.  Complain to them, not to the QEMU project.

Apple's not providing it on 10.6.x because 10.6.x is obsolete
as far as Apple is concerned. Supported versions of OSX use
clang, which has support for __thread. Missing __thread
support is an "old platform" thing, not a political GPL thing.

-- PMM

  reply	other threads:[~2015-01-24 19:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23 19:27 [Qemu-devel] qemu-coroutine.c: error: thread-local storage not supported for this target Programmingkid
2015-01-23 20:33 ` Paolo Bonzini
2015-01-23 20:39   ` Programmingkid
2015-01-23 20:55     ` Paolo Bonzini
2015-01-23 21:33       ` Programmingkid
2015-01-23 21:37         ` Paolo Bonzini
2015-01-23 21:48           ` Paolo Bonzini
2015-01-23 22:54             ` Programmingkid
2015-01-24 18:54               ` Paolo Bonzini
2015-01-24 19:33                 ` Peter Maydell [this message]
2015-01-24 19:59                   ` Paolo Bonzini

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='CAFEAcA8Jo+NPg-GuGi7-fSH9RoGHwKVgA5oq8ogbkzW0t4=c7w@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=programmingkidx@gmail.com \
    --cc=qemu-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.