From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:58130)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1Qr3dC-0004fS-5G
	for qemu-devel@nongnu.org; Wed, 10 Aug 2011 03:55:18 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1Qr3d7-0003wI-LM
	for qemu-devel@nongnu.org; Wed, 10 Aug 2011 03:55:14 -0400
Received: from mx1.redhat.com ([209.132.183.28]:50829)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1Qr3d7-0003vi-E5
	for qemu-devel@nongnu.org; Wed, 10 Aug 2011 03:55:09 -0400
Message-ID: <4E423957.8000703@redhat.com>
Date: Wed, 10 Aug 2011 09:55:03 +0200
From: Paolo Bonzini <pbonzini@redhat.com>
MIME-Version: 1.0
References: <218A230B8DDA47E0A817DCF708EB073F@FSCPC>
	<4E415E10.7090404@redhat.com>
	<2047BDFF62724C809C3E38C3CE16F94F@FSCPC>
In-Reply-To: <2047BDFF62724C809C3E38C3CE16F94F@FSCPC>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] coroutine-win32.c:36: error: thread-local storage
 not supported for this target
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Sebastian Herbszt <herbszt@gmx.de>
Cc: qemu-devel Developers <qemu-devel@nongnu.org>

On 08/09/2011 06:58 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...).

>
> I guess "gcc version 3.4.5 (mingw32 special)" is no longer supported then?
> What's the minimum gcc version needed now?

IIRC the next-newer GCC for mingw32 was 4.3, everything in the middle 
wasn't supported except by building it yourself.

Paolo