From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-104055-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 26500 invoked by alias); 14 Oct 2004 04:29:36 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Received: (qmail 26493 invoked from network); 14 Oct 2004 04:29:35 -0000
Received: from unknown (HELO smtp1.libero.it) (193.70.192.51)
  by sourceware.org with SMTP; 14 Oct 2004 04:29:35 -0000
Received: from localhost (172.16.1.79) by smtp1.libero.it (7.0.027-DD01)
        id 40C7315F019D63B5; Thu, 14 Oct 2004 06:29:38 +0200
Received: from bagio (151.37.66.24) by smtp2.libero.it (7.0.027-DD01)
        id 40CB2A0804F1AC39; Thu, 14 Oct 2004 06:29:49 +0200
Message-ID: <040101c4b1a6$6b7a2130$18422597@bagio>
From: "Giovanni Bajo" <giovannibajo@libero.it>
To: "Aaron W. LaFramboise" <aaronavay62@aaronwl.com>
Cc: <gcc@gcc.gnu.org>
References: <416DFF15.5080801@aaronwl.com>
Subject: Re: Questions on Bug Reporting
Date: Thu, 14 Oct 2004 09:37:00 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at libero.it serv1
X-SW-Source: 2004-10/txt/msg00553.txt.bz2

Aaron W. LaFramboise wrote:

> 1) If I find a bug, and figure out how to fix it right away, is it
> better to file a bug report in Bugzilla, or just post the patch to
> gcc-patches without opening a PR?

You can post directly a patch. Opening a PR is just a way to help you, to avoid
not losing track of it, etc. For instance, it might happen that the patch is
rejected and you do not want to rework it immediatly.

> 2) There are a whole lot of testsuite failures for the target I am
> primarily interested in, Windows.  After investigating a failure,
> should I file a bug report for it?  Should I submit patches to mark
> the PR as XFAIL if I don't immediately have a fix for it?

There is not a clear rule here, but it is a general agreement that we should
strive to stabilize on 0 unexpected failures. So, yes, the best thing is to
XFAIL them for Windows targets, file a PR about it and cross-reference the PR
in the testcase. This makes mostly sense if you analyze the regression though
so that you actually have something to write in the bug report.

Another very good thing you can do is always post your testsuite results to
gcc-testresults (through contrib/test_summary). The often, the better.

Thanks,
Giovanni Bajo