From: Gerd Hoffmann <kraxel@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: OpenBSD/Sparc64 gcc doesn't know about __thread, so build breaks
Date: Mon, 31 Aug 2009 08:46:33 +0200 [thread overview]
Message-ID: <4A9B71C9.30108@redhat.com> (raw)
In-Reply-To: <f43fc5580908290941j14db3e66y4117343b6431d3b8@mail.gmail.com>
On 08/29/09 18:41, Blue Swirl wrote:
> Hi,
>
> I get this error on OpenBSD/Sparc64:
> CC i386-softmmu/monitor.o
> /src/qemu/monitor.c:3232: error: thread-local storage not supported
> for this target
> gmake[1]: *** [monitor.o] Error 1
>
> Removing the offending __thread would fix the build.
Ok, just kill it then. I thought it is an easy way to make it
future-proof when qemu becomes more parallel. Right now we don't need
it though: even with io thread enabled the qemu code is protected by
one big lock, we don't have qemu code run truely parallel.
cheers,
Gerd
prev parent reply other threads:[~2009-08-31 6:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-29 16:41 [Qemu-devel] OpenBSD/Sparc64 gcc doesn't know about __thread, so build breaks Blue Swirl
2009-08-30 19:56 ` [Qemu-devel] " Sebastian Herbszt
2009-08-31 6:46 ` Gerd Hoffmann [this message]
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=4A9B71C9.30108@redhat.com \
--to=kraxel@redhat.com \
--cc=blauwirbel@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 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).