From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Blue Swirl <blauwirbel@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>, Roy Tam <roytam@gmail.com>
Subject: Re: [Qemu-devel] Compilation error of coroutine-win32.c with gcc version 3.4.5 (mingw-vista special r3)
Date: Wed, 17 Aug 2011 10:26:32 -0700 [thread overview]
Message-ID: <4E4BF9C8.5070205@redhat.com> (raw)
In-Reply-To: <CAJSP0QWKhfd8cU1XMO1BCd1pBzyXj1ibJFCRnq9c0xko2BUQ3A@mail.gmail.com>
On 08/17/2011 10:23 AM, Stefan Hajnoczi wrote:
>> > I don't know about Win32 TLS support, but at least OpenBSD/sparc64
>> > gcc/ld/ld.so/libc do not support __thread. According to manual, TLS is
>> > not available everywhere:
>> > http://gcc.gnu.org/onlinedocs/gcc-4.6.1/gcc/Thread_002dLocal.html#Thread_002dLocal
> Yeah, for OpenBSD we have the portable but slow GThread coroutine
> implementation.
I think (but I'm not sure) that a newer GCC on OpenBSD is able to
convert __thread to pthread_key_setspecific.
I'm trying to see if we can do something like Windows TLS at the
qemu-thread level.
Paolo
next prev parent reply other threads:[~2011-08-17 17:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-08 0:30 [Qemu-devel] Compilation error of coroutine-win32.c with gcc version 3.4.5 (mingw-vista special r3) Roy Tam
2011-08-08 6:21 ` Stefan Hajnoczi
2011-08-08 6:36 ` Roy Tam
2011-08-16 7:38 ` Roy Tam
2011-08-16 12:45 ` Stefan Hajnoczi
2011-08-16 18:50 ` Paolo Bonzini
2011-08-17 17:20 ` Blue Swirl
2011-08-17 17:23 ` Stefan Hajnoczi
2011-08-17 17:26 ` Paolo Bonzini [this message]
2011-08-18 3:36 ` Roy Tam
2011-08-20 8:41 ` Stefan Weil
2011-08-23 7:39 ` Roy Tam
2011-09-07 7:44 ` Roy Tam
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=4E4BF9C8.5070205@redhat.com \
--to=pbonzini@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=roytam@gmail.com \
--cc=stefanha@gmail.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).