From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14641 invoked by alias); 28 Dec 2002 17:41:49 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 14634 invoked from network); 28 Dec 2002 17:41:49 -0000 Received: from unknown (HELO e33.co.us.ibm.com) (32.97.110.131) by 209.249.29.67 with SMTP; 28 Dec 2002 17:41:49 -0000 Received: from westrelay03.boulder.ibm.com (westrelay03.boulder.ibm.com [9.17.194.24]) by e33.co.us.ibm.com (8.12.2/8.12.2) with ESMTP id gBSHfRTl035442; Sat, 28 Dec 2002 12:41:28 -0500 Received: from unknown.host (lig32-224-94-113.us.lig-dial.ibm.com [32.224.94.113]) by westrelay03.boulder.ibm.com (8.12.3/NCO/VER6.4) with ESMTP id gBSHfIr0095244; Sat, 28 Dec 2002 10:41:24 -0700 Received: (from janis@localhost) by unknown.host (8.9.3/8.9.3) id KAA01402; Fri, 27 Dec 2002 10:54:47 -0800 Date: Sat, 28 Dec 2002 11:48:00 -0000 From: Janis Johnson To: "Kaveh R. Ghazi" Cc: janis187@us.ibm.com, gcc@gcc.gnu.org Subject: Re: regression hunt status, question about reports to mailing list Message-ID: <20021227105447.A1393@us.ibm.com> References: <20021220091444.A1633@us.ibm.com> <200212262148.QAA18005@caip.rutgers.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200212262148.QAA18005@caip.rutgers.edu>; from ghazi@caip.rutgers.edu on Thu, Dec 26, 2002 at 04:48:31PM -0500 X-SW-Source: 2002-12/txt/msg01501.txt.bz2 On Thu, Dec 26, 2002 at 04:48:31PM -0500, Kaveh R. Ghazi wrote: > > From: Janis Johnson > > > > There are dozens more regressions to track down, including several for > > platforms that I can't test, particularly sparc. > > Janis > > Hi Janis, > > I was wondering if you could utilize your hunting method with a cross > compiler. If a given regression was e.g. an ICE and reproducable when > targetting the appropriate platform, if you were supplied with the .i > file and appropriate flags, then I'm thinking it should be possible. > > If so, would you be able to track down the critical patch point for > some of the sparc regressions I've filed? > > I.e. PRs 7227, 7794, 7796, perhaps more filed elsewhere by others. I > can supply the specific info and .i file if the PRs aren't enough. > > I think this would be a tremendously valuable addition to your already > helpful hunting. I was rather hoping that by providing information about how to do the hunts, as well as the framework script, other people would join in. I'm planning to go through my scripts that update cvs, do partial builds, and run tests to provide some representative examples of those, although they're all pretty straightforward. If no one else jumps in, though, I could try some searches with cross compilers; there's no reason that shouldn't work. I'm on vacation until January 2, occasionally running simple hunts while I'm doing vacation-type things at home. I'm running into several regressions whose searches turn up nonsensical patches. These are apparently bugs that show up randomly, rather than genuine regressions. Some of them get different results depending on whether I run them in the foreground or from a script. I'll look into those and report their behavior in GNATS. It's possible that some of the patches I've already reported also fall into that category. Janis