Re: target/6221: mips-irix6 gcc-3.1 testsuite failure in gcc.c-torture/execute/20020227-1.c

["Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>]

The following reply was made to PR target/6221; it has been noted by GNATS.

From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
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