Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
Message-ID: <BF35D9C143BCCC4EB63181B67C9320C804DD68@serv-075.icon-germany.local>
From: Heribert Dahms <heribert_dahms AT icon-gmbh DOT de>
To: "'Mumit Khan'" <khan AT NanoTech DOT Wisc DOT EDU>
Cc: cygwin-apps AT cygwin DOT com, cygwin AT cygwin DOT com
Subject: RE: pthreads support
Date: Tue, 27 Mar 2001 22:50:56 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain

Hi Mumit,

thanks for clarification! I've misinterpreted:

> Robert, The first "simple" testcase is gcc itself (configured with 
> --enable-threads=posix), since gcc uses a very small subset of pthreads
> functionality, and that's what I'm going to try as soon as I get a 
> chance to update my local tree.

and implied "gcc uses" as "gcc uses ... during compilation"
instead of "gcc supports"!

Bye, Heribert (heribert_dahms AT icon-gmbh DOT de)

> -----Original Message-----
> From:	Mumit Khan [SMTP:khan AT NanoTech DOT Wisc DOT EDU]
> Sent:	Tuesday, March 27, 2001 01:11
> To:	Heribert Dahms
> Cc:	cygwin-apps AT cygwin DOT com; cygwin AT cygwin DOT com
> Subject:	RE: pthreads support
> 
	[Heribert]  [snip]

> The GCC compilers and drivers are not multi-threaded, so you get no
> benefit from that. The multi-threading interface in gcc is needed to
> support thread-safe C++ exceptions (Java may need it too, but I know
> next to nothing about the GCC Java front-end).