From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10923 invoked by alias); 30 Nov 2012 04:02:37 -0000 Received: (qmail 10910 invoked by uid 22791); 30 Nov 2012 04:02:35 -0000 X-SWARE-Spam-Status: No, hits=-5.5 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Received: from mail-ea0-f175.google.com (HELO mail-ea0-f175.google.com) (209.85.215.175) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 30 Nov 2012 04:00:10 +0000 Received: by mail-ea0-f175.google.com with SMTP id h11so23503eaa.20 for ; Thu, 29 Nov 2012 20:00:09 -0800 (PST) MIME-Version: 1.0 Received: by 10.14.207.6 with SMTP id m6mr46587906eeo.10.1354248009344; Thu, 29 Nov 2012 20:00:09 -0800 (PST) Received: by 10.223.18.14 with HTTP; Thu, 29 Nov 2012 20:00:09 -0800 (PST) In-Reply-To: <92FF49B3-1180-4E33-BE04-ADE404BE8DC0@codesourcery.com> References: <06230AFE-EC8F-4F19-BFCF-E7D1D6DF6CBE@codesourcery.com> <92FF49B3-1180-4E33-BE04-ADE404BE8DC0@codesourcery.com> Date: Fri, 30 Nov 2012 04:02:00 -0000 Message-ID: Subject: Re: loop-unrolling in gcc-4.6.2 From: naga raj To: Maxim Kuvyrkov Cc: gcc-help Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2012-11/txt/msg00217.txt.bz2 On Fri, Nov 30, 2012 at 7:42 AM, Maxim Kuvyrkov wr= ote: > On 26/11/2012, at 9:31 PM, naga raj wrote: > >> On Mon, Nov 26, 2012 at 12:13 PM, Maxim Kuvyrkov wrote: >>> --param >> >> Thanks Maxim Kuvyrkov for your inputs. I have tried all the flags that >> you have suggested but they didn't help. >> >> As you suggested I will investigate where this loop-unrolling is >> blocked but are there any specific areas to be look in to the target >> regarding this?? > > I doubt you can productively troubleshoot this without a compiler built f= or debugging (i.e., non-boostrapped built with "-O0 -g"). When you have th= at, you can start stepping through loop optimizers and check why they are d= eciding not to unroll your loops. > > -- > Maxim Kuvyrkov > CodeSourcery / Mentor Graphics > Thanks Maxim. I will debug it as you suggested.