From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-prs-return-19616-listarch-gcc-prs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 3729 invoked by alias); 16 Jun 2002 15:26:03 -0000
Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc-prs/>
List-Post: <mailto:gcc-prs@gcc.gnu.org>
List-Help: <mailto:gcc-prs-help@gcc.gnu.org>
Sender: gcc-prs-owner@gcc.gnu.org
Received: (qmail 3714 invoked by uid 71); 16 Jun 2002 15:26:02 -0000
Date: Sun, 16 Jun 2002 11:56:00 -0000
Message-ID: <20020616152601.3713.qmail@sources.redhat.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
From: law@redhat.com
Subject: Re: c/7047: -march=2.0 often fails 
Reply-To: law@redhat.com
X-SW-Source: 2002-06/txt/msg00357.txt.bz2
List-Id: <gcc-prs.sourceware.org>

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

From: law@redhat.com
To: L-marks@nwu.edu
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c/7047: -march=2.0 often fails 
Date: Sun, 16 Jun 2002 09:27:29 -0600

 In message <20020616133812.31533.qmail@sources.redhat.com>, L-marks@nwu.edu wri
 tes:
  > 
  > >Number:         7047
  > >Category:       c
  > >Synopsis:       -march=2.0 often fails
  > >Confidential:   no
  > >Severity:       serious
  > >Priority:       medium
  > >Responsible:    unassigned
  > >State:          open
  > >Class:          sw-bug
  > >Submitter-Id:   net
  > >Arrival-Date:   Sun Jun 16 06:46:27 PDT 2002
  > >Closed-Date:
  > >Last-Modified:
  > >Originator:     L. D. Marks
  > >Release:        gcc 3.1
  > >Organization:
  > >Environment:
  > HPUX
  > >Description:
  > The PA 2.0 option -march=2.0 often fails, even with gcc code itself../../gcc
  > -3.1/gcc/sched-rgn.c: In function `init_ready_list':
  > Example of output
  > ../../gcc-3.1/gcc/sched-rgn.c:2569: insn does not satisfy its constraints:
  > (insn 1090 1088 106 (set (reg:SI 69 %fr22R)
  >         (mem/f:SI (lo_sum:SI (reg/f:SI 5 %r5 [142])
  >                 (symbol_ref:SI ("rgn_nr_edges"))) [3 rgn_nr_edges+0 S4 A32])
  > ) 68 {*pa.md:2088} (nil)
  >     (nil))
 Yes.  These bugs have been fixed for GCC 3.1.1
 
 jeff