From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29931 invoked by alias); 20 Sep 2009 03:37:24 -0000 Received: (qmail 29923 invoked by uid 22791); 20 Sep 2009 03:37:24 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 20 Sep 2009 03:37:18 +0000 Received: from int-mx05.intmail.prod.int.phx2.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.18]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n8K3bGp4026350; Sat, 19 Sep 2009 23:37:17 -0400 Received: from omfg.slc.redhat.com (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx05.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id n8K3bGHv016676; Sat, 19 Sep 2009 23:37:16 -0400 Message-ID: <4AB5A374.5080804@redhat.com> Date: Sun, 20 Sep 2009 03:37:00 -0000 From: Jeff Law User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.1) Gecko/20090814 Fedora/3.0-2.6.b3.fc11 Thunderbird/3.0b3 MIME-Version: 1.0 To: Nicolas Noble CC: gcc@gcc.gnu.org Subject: Re: Running gcc testsuite outside of gcc's sourcetree. References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2009-09/txt/msg00365.txt.bz2 On 09/19/09 18:14, Nicolas Noble wrote: > Hello, > > Long story short, I'm looking for a way to test a distribution's > compiler by running the latest gcc testsuite on it, but so far, I've > only seem to run it on the same gcc sourcetree it's on. I actually > wonder if it's possible and/or relevant to do this on the > distribution's compiler. > It's certainly possible. Under the hood the Makefile just invokes runtest. I don't think people do this that often anymore, so you might have to set some environment variables and/or set some paths, but when it's all said and done you can probably do something like cd /gcc/testsuite runtest --tool=gcc runtest --tool=g++ Which should run the gcc & g++ testsuites with your system compiler. > My problem resides in RedHat's gcc (which version seems to be gcc > (GCC) 4.1.2 20071124 (Red Hat 4.1.2-42)). I recently discovered that > this compiler hosts a bunch of known gcc bugs that have been reported > and fixed in the gcc mainstream, but it seems the bugfixes never got > ported back in RedHat's. > The fact of the matter is that every compiler has bugs. Backporting every bugfix to old releases isn't practical, particularly if the fix has the potential to introduce new regressions. It's a balancing act our engineers deal with daily. Customers (of course) have input into how we balance those decisions, and if you are a customer I would strongly encourage you to file a bug report with Red Hat. Jeff