From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16244 invoked by alias); 12 Jun 2002 16:56: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 16186 invoked by uid 71); 12 Jun 2002 16:56:01 -0000 Date: Wed, 12 Jun 2002 09:56:00 -0000 Message-ID: <20020612165601.16178.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Glen Nakamura Subject: Re: optimization/7001: gcc-3.1 and 3.04 on x86 generate bad memset code Reply-To: Glen Nakamura X-SW-Source: 2002-06/txt/msg00279.txt.bz2 List-Id: The following reply was made to PR optimization/7001; it has been noted by GNATS. From: Glen Nakamura To: adam@yggdrasil.com Cc: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org Subject: Re: optimization/7001: gcc-3.1 and 3.04 on x86 generate bad memset code Date: Wed, 12 Jun 2002 06:51:53 -1000 This bug report is similar to PR6703. You may want to try the CVS gcc-3_1-branch to see if it fixes your problem. You can find the patch for PR6703 here: http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6703 - Glen Nakamura