From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4277 invoked by alias); 17 Mar 2003 10:16: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 4257 invoked by uid 71); 17 Mar 2003 10:16:01 -0000 Date: Mon, 17 Mar 2003 10:16:00 -0000 Message-ID: <20030317101601.4245.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Bruno Haible Subject: Re: middle-end/6833: gcse generates wrong code with regard to global register variables Reply-To: Bruno Haible X-SW-Source: 2003-03/txt/msg01116.txt.bz2 List-Id: The following reply was made to PR middle-end/6833; it has been noted by GNATS. From: Bruno Haible To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: middle-end/6833: gcse generates wrong code with regard to global register variables Date: Mon, 17 Mar 2003 11:10:38 +0100 (CET) Wolfgang writes: > Synopsis: gcse generates wrong code with regard to global register variables > > State-Changed-From-To: open->feedback > State-Changed-By: bangerth > State-Changed-When: Sat Mar 15 03:21:07 2003 > State-Changed-Why: > Bruno, I don't have 3.1 around any more, but I can't > reproduce this with 3.2 and 3.2.2. Still, could you add my testcase to the testsuite? Global register variables are not used by many programs, but GNU clisp relies on them very much. I'd like to not see this bug appear again. Bruno