From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 72095 invoked by alias); 7 Apr 2015 17:36:02 -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 Received: (qmail 72009 invoked by uid 48); 7 Apr 2015 17:35:58 -0000 From: "law at redhat dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/29256] [4.8/4.9/5 regression] loop performance regression Date: Tue, 07 Apr 2015 17:36:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 4.2.0 X-Bugzilla-Keywords: missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: law at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.8.5 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-04/txt/msg00449.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29256 --- Comment #49 from Jeffrey A. Law --- Richi, see c#45. Basically the regression is "gone" for the testcase as-is... But it's pretty easy to twiddle it slightly and show the regression. It's also important to note this is e500 code, so you need to configure your toolchain appropriately.