public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gdr at integrable-solutions dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/19401] Trivial loop not unrolled
Date: Wed, 12 Jan 2005 17:06:00 -0000	[thread overview]
Message-ID: <20050112170635.10010.qmail@sourceware.org> (raw)
In-Reply-To: <20050112160800.19401.rguenth@tat.physik.uni-tuebingen.de>


------- Additional Comments From gdr at integrable-solutions dot net  2005-01-12 17:06 -------
Subject: Re:  Trivial loop not unrolled

"rguenth at tat dot physik dot uni-tuebingen dot de" <gcc-bugzilla@gcc.gnu.org> writes:

| Or stuff often found in C++ libraries:
| 
| template <int Dim>
| struct Vector
| {
|   Vector(float init)
|   {
|     for (int i=0; i<Dim; ++i)
|       v[i] = init;
|   }
|   float v[Dim];
| };
| 
| for small Dim (<= 4 should make nearly everyone happy) you want all the
| dimension-unaware loops to be unrolled.

I agree.

-- Gaby


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19401


  parent reply	other threads:[~2005-01-12 17:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-12 16:08 [Bug tree-optimization/19401] New: " rguenth at tat dot physik dot uni-tuebingen dot de
2005-01-12 16:10 ` [Bug tree-optimization/19401] " rguenth at tat dot physik dot uni-tuebingen dot de
2005-01-12 16:14 ` pinskia at gcc dot gnu dot org
2005-01-12 16:19 ` rguenth at tat dot physik dot uni-tuebingen dot de
2005-01-12 16:21 ` pinskia at gcc dot gnu dot org
2005-01-12 16:24 ` rguenth at tat dot physik dot uni-tuebingen dot de
2005-01-12 17:05 ` gdr at integrable-solutions dot net
2005-01-12 17:06 ` gdr at integrable-solutions dot net [this message]
2005-01-13 13:48 ` pinskia at gcc dot gnu dot org
2005-01-14  9:04 ` rakdver at gcc dot gnu dot org
2005-01-24  9:43 ` rguenth at tat dot physik dot uni-tuebingen dot de
2005-05-06 21:11 ` cvs-commit at gcc dot gnu dot org
2005-05-07 19:56 ` pinskia at gcc dot gnu dot org

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=20050112170635.10010.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).