From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13798 invoked by alias); 27 Mar 2003 12: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 13660 invoked by uid 71); 27 Mar 2003 12:36:01 -0000 Date: Thu, 27 Mar 2003 13:07:00 -0000 Message-ID: <20030327123601.13659.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Eric Botcazou Subject: Re: target/8819: [sparc] G++ generates code with unresolved internal label Reply-To: Eric Botcazou X-SW-Source: 2003-03/txt/msg01895.txt.bz2 List-Id: The following reply was made to PR target/8819; it has been noted by GNATS. From: Eric Botcazou To: Torbjorn Granlund Cc: gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: target/8819: [sparc] G++ generates code with unresolved internal label Date: Thu, 27 Mar 2003 13:30:15 +0100 > Have you tried reproducing it with the setup suggested in the > PR? As I trust you know, a different compiler version might > not stumple on a certain test case, even if the bug is still there. Did I not use the exact same setup (as far as gcc is concerned though) as yours? What is the error produced on your system? -- Eric Botcazou