public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: naga raj <gnuuser.raj@gmail.com>
To: Maxim Kuvyrkov <maxim@codesourcery.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: loop-unrolling in gcc-4.6.2
Date: Mon, 26 Nov 2012 08:31:00 -0000	[thread overview]
Message-ID: <CAKuVEhCq5RHDvKziTX9kaXo8jrT+JeHNXrWnJe+n8JTRMqRBDg@mail.gmail.com> (raw)
In-Reply-To: <06230AFE-EC8F-4F19-BFCF-E7D1D6DF6CBE@codesourcery.com>

On Mon, Nov 26, 2012 at 12:13 PM, Maxim Kuvyrkov <maxim@codesourcery.com> 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??

Thanks,
Nagaraju

  reply	other threads:[~2012-11-26  8:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-23 15:02 naga raj
2012-11-26  6:43 ` Maxim Kuvyrkov
2012-11-26  8:31   ` naga raj [this message]
2012-11-30  2:13     ` Maxim Kuvyrkov
2012-11-30  4:02       ` naga raj

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAKuVEhCq5RHDvKziTX9kaXo8jrT+JeHNXrWnJe+n8JTRMqRBDg@mail.gmail.com \
    --to=gnuuser.raj@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=maxim@codesourcery.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).