public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Igor Schein <igor@txc.com>
To: help-gcc@gnu.org
Subject: -funroll-all-loops
Date: Fri, 07 Jan 2000 17:07:00 -0000	[thread overview]
Message-ID: <20000107200836.G21972@dione.txc.com> (raw)

Hi,

I have a question about the following segment of info pages
for gcc:

`-funroll-all-loops'
     Perform the optimization of loop unrolling.  This is done for all
     loops and usually makes programs run more slowly.
     `-funroll-all-loops' implies `-fstrength-reduce' as well as
     `-frerun-cse-after-loop'.

Does 
"usually makes programs run more slowly" 
imply 
"however, for some rare cases it _will_ make them run faster"?  

If it doesn't, then I don't see a point of using this flag at all.

Thanks

Igor

WARNING: multiple messages have this Message-ID

From: Igor Schein <igor@txc.com>
To: help-gcc@gnu.org
Subject: -funroll-all-loops
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <20000107200836.G21972@dione.txc.com> (raw)
Message-ID: <20000401000000.CEjZcHXGSn9V9kvZ1xyVIUmZLAVDbfBZp31BNVDvwzk@z> (raw)

Hi,

I have a question about the following segment of info pages
for gcc:

`-funroll-all-loops'
     Perform the optimization of loop unrolling.  This is done for all
     loops and usually makes programs run more slowly.
     `-funroll-all-loops' implies `-fstrength-reduce' as well as
     `-frerun-cse-after-loop'.

Does 
"usually makes programs run more slowly" 
imply 
"however, for some rare cases it _will_ make them run faster"?  

If it doesn't, then I don't see a point of using this flag at all.

Thanks

Igor

             reply	other threads:[~2000-01-07 17:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-07 17:07 Igor Schein [this message]
2000-04-01  0:00 ` -funroll-all-loops Igor Schein

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=20000107200836.G21972@dione.txc.com \
    --to=igor@txc.com \
    --cc=help-gcc@gnu.org \
    /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).