From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12712 invoked by alias); 28 Mar 2003 10:49:56 -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 12693 invoked by uid 48); 28 Mar 2003 10:49:55 -0000 Date: Fri, 28 Mar 2003 11:30:00 -0000 Message-ID: <20030328104955.12692.qmail@sources.redhat.com> To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, philb@gnu.org, rearnsha@gcc.gnu.org From: rearnsha@gcc.gnu.org Reply-To: rearnsha@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, philb@gnu.org, rearnsha@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: target/843: [ARM] g77 `Unrecognizable insn' from const_double with -fPIC X-SW-Source: 2003-03/txt/msg01991.txt.bz2 List-Id: Synopsis: [ARM] g77 `Unrecognizable insn' from const_double with -fPIC State-Changed-From-To: analyzed->closed State-Changed-By: rearnsha State-Changed-When: Fri Mar 28 10:49:55 2003 State-Changed-Why: GCC 3.3 and current no-longer have a chain of CONST_DOUBLE values stored inside the CONST_DOUBLE rtx, so this problem can no longer occur. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=843