From: Stefan Hajnoczi <stefanha@gmail.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.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 18:23:23 +0100 [thread overview]
Message-ID: <CAJSP0QWKhfd8cU1XMO1BCd1pBzyXj1ibJFCRnq9c0xko2BUQ3A@mail.gmail.com> (raw)
In-Reply-To: <CAAu8pHuU9ukz6QOLbm=_tFTUECNNu3qrzMM5+ovpnzHYv5LafQ@mail.gmail.com>
On Wed, Aug 17, 2011 at 6:20 PM, Blue Swirl <blauwirbel@gmail.com> wrote:
> On Tue, Aug 16, 2011 at 6:50 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>> On 08/16/2011 05:45 AM, Stefan Hajnoczi wrote:
>>>
>>> Roy,
>>> This stack trace does not reveal much.
>>>
>>> Is there any MinGW gcc user that has successfully built and run
>>> qemu.git?
>>
>> I would be surprised if Stefan Weil hasn't.
>
> Builds and runs (under i386 chroot + Wine) here. It worked also in
> Windows the last time I tried (2010).
>
>>> Which version/architecture of Windows and which MinGW
>>> version?
>
> Debian:
> $ i586-mingw32msvc-gcc -v
> Using built-in specs.
> Target: i586-mingw32msvc
> Configured with:
> /build/buildd-gcc-mingw32_4.4.4-0.1+b1-amd64-aFhFbL/gcc-mingw32-4.4.4/build-tree/gcc-4.4.4/configure
> --build=x86_64-linux-gnu --prefix=/usr --includedir='/usr/include'
> --mandir='/usr/share/man' --infodir='/usr/share/info'
> --sysconfdir=/etc --localstatedir=/var
> --libexecdir='/usr/lib/gcc-mingw32' --disable-multilib
> --enable-threads --enable-sjlj-exceptions
> --enable-version-specific-runtime-libs --disable-shared
> --target=i586-mingw32msvc --enable-languages=c,c++,fortran :
> (reconfigured) /build/buildd-gcc-mingw32_4.4.4-0.1+b1-amd64-aFhFbL/gcc-mingw32-4.4.4/build-tree/gcc-4.4.4/configure
> --build=x86_64-linux-gnu --prefix=/usr --includedir='/usr/include'
> --mandir='/usr/share/man' --infodir='/usr/share/info'
> --sysconfdir=/etc --localstatedir=/var
> --libexecdir='/usr/lib/gcc-mingw32' --disable-multilib
> --enable-threads --enable-sjlj-exceptions
> --enable-version-specific-runtime-libs --disable-shared
> --target=i586-mingw32msvc --enable-languages=c,c++,fortran
> Thread model: win32
> gcc version 4.4.4 (GCC)
>
> Compiled myself:
> $ i686-mingw32msvc-gcc -v
> Using built-in specs.
> COLLECT_GCC=i686-mingw32msvc-gcc
> COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/i686-mingw32msvc/4.6.0/lto-wrapper
> Target: i686-mingw32msvc
> Configured with: ../configure --target=i686-mingw32msvc
> --enable-targets=i686-mingw32msvc --disable-nls --disable-threads
> --enable-languages=c --disable-shared --disable-libssp
> --disable-multilib
> Thread model: single
> gcc version 4.6.0 20100925 (experimental) (GCC)
>
>> I'm trying to get rid of emutls, it is slow anyway and we'll likely want to
>> rely on TLS very liberally in the future. If it fixes the bug, we can
>> backport it to stable too.
>
> 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.
Stefan
next prev parent reply other threads:[~2011-08-17 17:23 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 [this message]
2011-08-17 17:26 ` Paolo Bonzini
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=CAJSP0QWKhfd8cU1XMO1BCd1pBzyXj1ibJFCRnq9c0xko2BUQ3A@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=blauwirbel@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=roytam@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).