From: Zdenek Dvorak <rakdver@kam.mff.cuni.cz>
To: Jean Christophe Beyler <jean.christophe.beyler@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Turning off unrolling to certain loops
Date: Thu, 08 Oct 2009 16:23:00 -0000 [thread overview]
Message-ID: <20091008161802.GA30141@kam.mff.cuni.cz> (raw)
In-Reply-To: <c568a2600910080722k794552fvbde46fed95601b21@mail.gmail.com>
Hi,
> 2) I was using a simple example:
>
> #pragma unroll 2
> for (i=0;i<6;i++)
> {
> printf ("Hello world\n");
> }
>
> If I do this, instead of transforming the code into :
> for (i=0;i<3;i++)
> {
> printf ("Hello world\n");
> printf ("Hello world\n");
> }
>
> as we could expect, it is transformed into:
> for (i=0;i<2;i++)
> {
> printf ("Hello world\n");
> printf ("Hello world\n");
> }
> for (i=0;i<2;i++)
> {
> printf ("Hello world\n");
> }
>
>
> (I am using 4.3.2 currently)
>
> I am using the tree_unroll_loop function to perform the unrolling and
> it seems to always want to keep that epilogue. Is there a reason for
> this? Or is this a bug of some sorts?
such an epilogue is needed when the # of iterations is not known in the
compile time; it should be fairly easy to modify the unrolling not to
emit it when it is not necessary,
Zdenek
next prev parent reply other threads:[~2009-10-08 16:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 20:46 Jean Christophe Beyler
2009-10-06 6:54 ` Zdenek Dvorak
2009-10-06 13:34 ` Jean Christophe Beyler
[not found] ` <20091006135624.GA18714@kam.mff.cuni.cz>
[not found] ` <c568a2600910060756m96adf86mb1507c6717fdfdb6@mail.gmail.com>
[not found] ` <20091006150918.GA19277@kam.mff.cuni.cz>
[not found] ` <c568a2600910060828l24ec5ecct926eb2624a1d2157@mail.gmail.com>
2009-10-08 16:18 ` Jean Christophe Beyler
2009-10-08 16:23 ` Zdenek Dvorak [this message]
2009-10-08 18:52 ` Jean Christophe Beyler
2009-10-14 18:56 ` Jean Christophe Beyler
2009-10-15 0:45 ` Zdenek Dvorak
2009-10-15 10:00 ` Bingfeng Mei
2009-10-15 14:41 ` Zdenek Dvorak
2009-10-15 15:56 ` Jean Christophe Beyler
2009-10-15 16:27 ` Bingfeng Mei
2009-10-15 17:16 ` Jean Christophe Beyler
2009-10-16 12:17 ` Bingfeng Mei
2009-10-16 13:51 ` Jean Christophe Beyler
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=20091008161802.GA30141@kam.mff.cuni.cz \
--to=rakdver@kam.mff.cuni.cz \
--cc=gcc@gcc.gnu.org \
--cc=jean.christophe.beyler@gmail.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).