From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9319 invoked by alias); 11 Feb 2009 17:03:27 -0000 Received: (qmail 9102 invoked by uid 22791); 11 Feb 2009 17:03:25 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from smtp113.sbc.mail.re2.yahoo.com (HELO smtp113.sbc.mail.re2.yahoo.com) (68.142.229.92) by sourceware.org (qpsmtpd/0.43rc1) with SMTP; Wed, 11 Feb 2009 17:03:19 +0000 Received: (qmail 81207 invoked from network); 11 Feb 2009 17:03:17 -0000 Received: from unknown (HELO ?10.251.73.40?) (TimothyPrince@192.55.60.73 with plain) by smtp113.sbc.mail.re2.yahoo.com with SMTP; 11 Feb 2009 17:03:16 -0000 Message-ID: <499304D2.1000908@sbcglobal.net> Date: Wed, 11 Feb 2009 17:03:00 -0000 From: Tim Prince Reply-To: tprince@computer.org User-Agent: Thunderbird 2.0.0.19 (X11/20081227) MIME-Version: 1.0 To: Robert Jones CC: tprince@computer.org, gcc-help@gcc.gnu.org Subject: Re: g++ versions References: <4efd67eb0902110513j323585d1s8a6e1899647f00ca@mail.gmail.com> <4992E13C.3010903@sbcglobal.net> <4efd67eb0902110730k1b1040a6g4f679c11215e0105@mail.gmail.com> In-Reply-To: <4efd67eb0902110730k1b1040a6g4f679c11215e0105@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2009-02/txt/msg00078.txt.bz2 Robert Jones wrote: > I'm unclear what you mean by the Cygwin install menu - is that the setup > program? Yes, cygwin setup menu has included g++-4 and its cousins for several months. > > My aim is simply to arrive at fairly recent (ie version 4) g++ compiler for > Windows, either a binary download or one I build myself, but the build > reports seem to suggest that all the v4 windows build attempts have many > failures. Well, let's be more specific. Windows targets are at best secondary for gcc. This means the gcc developers have latitude about the degree of Windows support in testsuite for each front end. Out of 13 failures in the g++ section of gcc-testsuite for cygwin in last Friday's gcc-4.4 snapshot, 9 are due to minor formatting discrepancies between the linux and Windows versions of .s file. Let's give the g++ people some credit for major progress. Most of the libstdc++ testsuite failures are due to the broken scheme in testsuite of attempting to link against libiconv. Many people don't care about libiconv, which probably bears on why it isn't fixed. The gcc people don't care to make testsuite entirely meaningful on Windows. In addition to testing functionality which will never be supported on Windows, without marking those tests as XFAIL, and not allowing the bsd variations of tests rather than linux ones to be used for Windows, there are major categories of Windows failures, e.g. pch, vectorization (even though vectorization basically works). The greatest gross number of failures I have seen in repetitions of gcc testsuite is 177, out of more than 20000. If you prefer a version of gcc which hasn't been run through testsuite publically, be my guest. The gfortran tests which fail are all OS-specific, and have been discussed on the gfortran list. objc testsuite gives the same results as on most primary targets. gomp testsuite, if enabled, doesn't give many errors. That doesn't necessarily translate into a reliable option. After all, it's built on pthreads without much specific Windows stuff, aside from the proprietary mingw offering with an alternate library of unknown origin or licensing compliance. mingw versions of gcc often have major gaps in exception handling, fast-math, profiling, and thread support, so there are many expected testsuite failures. That doesn't make them unusable, within their limits. You certainly can't expect the testsuite cases which test for presence of glibc specific directories to pass on Windows. I'll post this week's gcc-testsuite for cygwin soon. Have to decide whether to let it complete the extra rounds it chooses to make when there are failures. Do you care about work-arounds for building gcc on cygwin?