Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3D325399.6090506@ece.gatech.edu> Date: Mon, 15 Jul 2002 00:46:17 -0400 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 CC: cygwin AT cygwin DOT com Subject: Re: Available for test: gcc-3.1.1-2 gcc2-2.95.3-8 References: <20020711044304 DOT GA3292 AT redhat DOT com> <3D2D3205 DOT 7080606 AT ece DOT gatech DOT edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Question about threading models for -mno-cygwin: Since the cygwin compiler is built using --enable-threads=posix, how does that affect the compiler in -mno-cygwin mode, and the mingw version of the stdc++ library in /usr/lib/mingw ? I would assume that the "normal" mingw compiler uses --enable-threads=win32. Does that mean that code (libraries) built using MINGW's g++ aren't usable by cygwin's g++ in -mno-cygwin mode (and vice versa)? Also, I've seen repeated references that "mingw's compiler will be built with dwarf2 exceptions". I assume that there are only two versions of EH code: dwarf2 and sjlj -- and you only get sjlj if you use --enable-sjlj-exceptions or somesuch? (If so, then the "regular" mingw build -- which is claimed to be use dwarf2 EH, and the cygiwn build will both have dwarf2 EH, since mknetrel/extra/gcc *doesn't* say --enable-sjlj...) Which is good. If I'm right. --Chuck -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/