Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Mon, 15 Jul 2002 01:20:13 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Available for test: gcc-3.1.1-2 gcc2-2.95.3-8 Message-ID: <20020715052013.GA18499@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20020711044304.GA3292@redhat.com> <3D2D3205.7080606@ece.gatech.edu> <3D325399.6090506@ece.gatech.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D325399.6090506@ece.gatech.edu> User-Agent: Mutt/1.3.23.1i On Mon, Jul 15, 2002 at 12:46:17AM -0400, Charles Wilson wrote: >Question about threading models for -mno-cygwin: Threading should work correctly for either the -mno-cygwin or the -mcygwin cases. >Also, I've seen repeated references that "mingw's compiler will be built >with dwarf2 exceptions". Cygwin and mingw are using the same code base now. So both use dwarf2 exceptions. >(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. Right. I've actually mentioned this in a previous message and I'm sure I'll be mentioning it again. Maybe we need a GCC FAQ. Or maybe the (currently nonexistent) gcc README should mention this. FWIW, I'm on build #4010 right now. "gcc -mno-cygwin -E" wasn't working right. cgf -- 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/