From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10673 invoked by alias); 13 Jan 2011 10:55:28 -0000 Received: (qmail 10663 invoked by uid 22791); 13 Jan 2011 10:55:28 -0000 X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 13 Jan 2011 10:55:24 +0000 From: "rguenther at suse dot de" To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/43494] [4.4/4.5/4.6 Regression] Overlooked dependency causes wrong scheduling, wrong code X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: rtl-optimization X-Bugzilla-Keywords: alias, wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenther at suse dot de X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.4.6 X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Date: Thu, 13 Jan 2011 10:56:00 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2011-01/txt/msg01240.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43494 --- Comment #29 from rguenther at suse dot de 2011-01-13 10:55:01 UTC --- On Thu, 13 Jan 2011, aoliva at gcc dot gnu.org wrote: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43494 > > --- Comment #28 from Alexandre Oliva 2011-01-13 10:31:21 UTC --- > Created attachment 22957 > --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22957 > Updated patch, still awaiting review > > The patch to fix this bug, posted on Sept 21, is still awaiting review :-( > > This updated version fixes just a whitespace difference that caused it to fail > to apply. I suppose pinging it on the ML is better than pinging it here.