From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:57963)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <brad@comstyle.com>) id 1QtprG-00014h-Gh
	for qemu-devel@nongnu.org; Wed, 17 Aug 2011 19:49:19 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <brad@comstyle.com>) id 1Qtpr1-0000DC-NK
	for qemu-devel@nongnu.org; Wed, 17 Aug 2011 19:49:09 -0400
Received: from speedy.comstyle.com ([206.51.28.2]:22533 helo=mail.comstyle.com)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <brad@comstyle.com>) id 1Qtpr1-0000D2-Kx
	for qemu-devel@nongnu.org; Wed, 17 Aug 2011 19:48:59 -0400
From: Brad <brad@comstyle.com>
References: <1313520667-26507-1-git-send-email-pbonzini@redhat.com>
	<4E4B4557.2050505@comstyle.com> <4E4B65CB.70603@redhat.com>
	<CAAu8pHuWJMvXr6D=zJTyrDPLiG-eruyZAgCjnZOez8HdA7DUAQ@mail.gmail.com>
	<4E4C0FCF.4030901@twiddle.net>
In-Reply-To: <4E4C0FCF.4030901@twiddle.net>
Content-Type: text/plain; charset=utf-8
Content-ID: <1313625016.1478.5.camel@Nokia-N900>
Date: Wed, 17 Aug 2011 19:50:17 -0400
Message-Id: <1313625017.1478.6.camel@Nokia-N900>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PATCH] qemu-thread: add TLS wrappers
Reply-To: Brad <brad@comstyle.com>
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: Richard Henderson <rth@twiddle.net>, Blue Swirl <blauwirbel@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org

----- Original message -----
> On 08/17/2011 10:28 AM, Blue Swirl wrote:
> > GCC may support it but it can't use it on a platform if the other
> > parts are missing (libc etc.).
> 
> With a new-enough gcc, we provide the support in libgcc.

I doubt gcc 4.2.1 fits the bill.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.