qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Sebastian Herbszt <herbszt@gmx.de>
Cc: qemu-devel Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] coroutine-win32.c:36: error: thread-local storage not supported for this target
Date: Tue, 09 Aug 2011 18:19:28 +0200	[thread overview]
Message-ID: <4E415E10.7090404@redhat.com> (raw)
In-Reply-To: <218A230B8DDA47E0A817DCF708EB073F@FSCPC>

On 08/09/2011 05:53 PM, Sebastian Herbszt wrote:
> CC coroutine-win32.o
> coroutine-win32.c:36: error: thread-local storage not supported for this
> target
> coroutine-win32.c:37: error: thread-local storage not supported for this
> target
> make: *** [coroutine-win32.o] Error 1

You need a newer GCC.  Alternatively we can change it to use 
TlsAlloc/TlsFree, but I would like to support __thread-based TLS always 
(for example for liburcu---userspace RCU...).

Paolo

  reply	other threads:[~2011-08-09 16:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-09 15:53 [Qemu-devel] coroutine-win32.c:36: error: thread-local storage not supported for this target Sebastian Herbszt
2011-08-09 16:19 ` Paolo Bonzini [this message]
2011-08-09 16:58   ` Sebastian Herbszt
2011-08-10  7:55     ` 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=4E415E10.7090404@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=herbszt@gmx.de \
    --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 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).