From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22887 invoked by alias); 25 Apr 2003 00:46:02 -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 22817 invoked by uid 71); 25 Apr 2003 00:46:01 -0000 Date: Fri, 25 Apr 2003 00:46:00 -0000 Message-ID: <20030425004601.22793.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Wolfgang Bangerth Subject: optimization/4490 Reply-To: Wolfgang Bangerth X-SW-Source: 2003-04/txt/msg01069.txt.bz2 List-Id: The following reply was made to PR optimization/4490; it has been noted by GNATS. From: Wolfgang Bangerth To: rth@gnu.gcc.org Cc: gcc-gnats@gcc.gnu.org Subject: optimization/4490 Date: Thu, 24 Apr 2003 19:43:29 -0500 (CDT) Richard, I just closed a report for which I found that it is a duplicate of 4490. What startles me with that one is that it is suspended. What is the reason for that? If this just waits for someone to fix it, I think we'd better leave it analyzed. "suspended" only seems like the proper choice when we are waiting for external events to happen (resolution of a standard defect report, branch to merge, etc). Thanks Wolfgang ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ices.utexas.edu www: http://www.ices.utexas.edu/~bangerth/