From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 898 invoked by alias); 14 Apr 2002 17:36:01 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 884 invoked by uid 71); 14 Apr 2002 17:36:01 -0000 Date: Sun, 14 Apr 2002 10:36:00 -0000 Message-ID: <20020414173601.883.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: "Kaveh R. Ghazi" Subject: Re: target/6221: mips-irix6 gcc-3.1 testsuite failure in gcc.c-torture/execute/20020227-1.c Reply-To: "Kaveh R. Ghazi" X-SW-Source: 2002-04/txt/msg00749.txt.bz2 List-Id: The following reply was made to PR target/6221; it has been noted by GNATS. From: "Kaveh R. Ghazi" To: David.Billinghurst@riotinto.com, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, rth@gcc.gnu.org, rth@redhat.com Cc: Subject: Re: target/6221: mips-irix6 gcc-3.1 testsuite failure in gcc.c-torture/execute/20020227-1.c Date: Sun, 14 Apr 2002 13:28:11 -0400 (EDT) > From: rth@gcc.gnu.org > > Synopsis: mips-irix6 gcc-3.1 testsuite failure in gcc.c-torture/execute/20020227-1.c > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6221 > > > It's a reload problem common to _all_ 64-bit targets. So what is the prognosis doctor? Fixable by 3.1 release? > Why all the separate PRs for failing test cases anyway? Well if they are from the same root cause, one can close them and set the "class" field to "duplicate" with an explanation and a pointer to the original report. However if they're not, then they warrent a separate PR. It probably wasn't readily apparent to the filer whether these were duplicates of some other filed problem report. (Are they?) --Kaveh -- Kaveh R. Ghazi Director of Systems Architecture ghazi@caip.rutgers.edu Qwest Global Services