X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org Message-ID: <4BCE3B5D.2020909@gmail.com> Date: Wed, 21 Apr 2010 00:40:13 +0100 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: gcc: building gcc-4.5.0 for Cygwin References: <87y6go3743.fsf@gmail.com> <4BC904E3.60500@verizon.net> <878w8lx1kt.fsf@gmail.com> <4BCD9A2A.9060906@gmail.com> <87eii92aac.fsf@gmail.com> In-Reply-To: <87eii92aac.fsf@gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: 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 On 20/04/2010 20:28, Paul Bibbings wrote: > (BTW. I'm guessing by "That'd be my fault" that you're working on gcc > upstream?) I certainly am; my long-term goal is a) to synchronize upstream and downstream so that in the end there are no cygwin-specific patches needed and anyone can just build the plain sources from upstream and get a fully compatible compiler that generates fully compatible executables, and b) to add any missing support so that we can get features like LTO and graphite working. I think we're fairly close to there already, but there might be some minor incompatibilities in odd corners of C++ related to typeinfos and dynamic typecasts. cheers, DaveK -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple