From: Paolo Bonzini <pbonzini@redhat.com>
To: Bug 932487 <932487@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 932487] Re: win32: git rev 59f971d crashes when accessing disk (coroutine issue)
Date: Tue, 20 Mar 2012 10:57:59 +0100 [thread overview]
Message-ID: <4F6854A7.2000906@redhat.com> (raw)
In-Reply-To: <CAA=zYJa8j2paRAS1r3PPrqw4rVFfD6g2ZWERtS6Zow8FPKw16g@mail.gmail.com>
Il 20/03/2012 10:35, Roy Tam ha scritto:
> 2012/3/20 Stefan Weil <932487@bugs.launchpad.net>:
>> Please try a newer compiler. gcc-4.6.2 compiles thread local storage correctly, gcc-4.3.3 obviously doesn't.
>> If you can confirm that newer compilers fix this bug, I'd like to close this ticket.
>
> I'm using gcc-4.6.2 now.
Please test this suggestion:
>>> Please try these modified configure option which adds the compiler flag needed for multithreading:
>>> --extra-cflags="-O0 -pipe -mthreads". For me, -mthreads solved the problem.
>>
>> Yes "-mthreads" switch does workaround the issue.
>> But using "-mthreads" making resulting binaries depend on
>> mingwm10.dll, which is not good.
>
> Is "-D_MT" enough instead of -mthreads?
Paolo
next prev parent reply other threads:[~2012-03-20 9:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 1:59 [Qemu-devel] [Bug 932487] [NEW] win32: git rev 59f971d crashes when accessing disk (coroutine issue) Roy Tam
2012-02-15 7:15 ` [Qemu-devel] [Bug 932487] " Roy Tam
2012-02-16 9:34 ` [Qemu-devel] [Bug 932487] [NEW] " Stefan Hajnoczi
2012-02-16 10:34 ` Kevin Wolf
2012-02-16 10:56 ` Roy Tam
2012-02-16 11:01 ` Paolo Bonzini
2012-02-16 11:15 ` Kevin Wolf
2012-02-16 13:13 ` Roy Tam
2012-02-16 16:05 ` Paolo Bonzini
2012-02-16 20:31 ` [Qemu-devel] [Bug 932487] " Stefan Weil
2012-02-16 20:42 ` Stefan Weil
2012-02-17 0:53 ` Roy Tam
2012-02-17 1:00 ` Roy Tam
2012-02-27 16:04 ` Paolo Bonzini
2012-02-27 15:17 ` Eric Lassauge
2012-03-20 6:38 ` Roy Tam
2012-03-20 9:07 ` Stefan Weil
2012-03-20 9:35 ` Roy Tam
2012-03-20 9:57 ` Paolo Bonzini [this message]
2016-12-11 7:19 ` Stefan Weil
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=4F6854A7.2000906@redhat.com \
--to=pbonzini@redhat.com \
--cc=932487@bugs.launchpad.net \
--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.