From: Mike Stump <mikestump@comcast.net>
To: Richard Biener <richard.guenther@gmail.com>
Cc: gcc-patches Patches <gcc-patches@gcc.gnu.org>,
Jason Merrill <jason@redhat.com>,
"Joseph S. Myers" <joseph@codesourcery.com>
Subject: Re: #pragma GCC unroll support
Date: Mon, 26 Jan 2015 21:18:00 -0000 [thread overview]
Message-ID: <F9073DC4-1F6C-473B-83DA-6D012AB6F08B@comcast.net> (raw)
In-Reply-To: <9FE5AF27-EB8A-4CC3-A345-A69C2BFD8F30@comcast.net>
[-- Attachment #1: Type: text/plain, Size: 79 bytes --]
I missed including the documentation patch in the last set. :-( Here it is:
[-- Attachment #2: unroll-3e-doc.diffs.txt --]
[-- Type: text/plain, Size: 748 bytes --]
Index: extend.texi
===================================================================
--- extend.texi (revision 220084)
+++ extend.texi (working copy)
@@ -17881,6 +17881,17 @@ void ignore_vec_dep (int *a, int k, int
@}
@end smallexample
+@table @code
+@item #pragma GCC unroll @var{"n"}
+@cindex pragma GCC unroll @var{"n"}
+
+With this pragma, the programmer informs the optimizer how many times
+a loop should be unrolled. A 0 or 1 informs the compiler to not
+perform any loop unrolling. The pragma must be immediately before
+@samp{#pragma ivdep} or a @code{for}, @code{while} or @code{do} loop
+and applies only to the loop that follows.
+
+@end table
@node Unnamed Fields
@section Unnamed struct/union fields within structs/unions
next prev parent reply other threads:[~2015-01-26 19:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 21:51 Mike Stump
2014-12-23 20:22 ` Andi Kleen
2015-01-08 12:45 ` Richard Biener
2015-01-26 21:13 ` Mike Stump
2015-01-26 21:18 ` Mike Stump [this message]
2015-01-30 2:51 ` Joseph Myers
2015-01-30 6:12 ` Mike Stump
2015-01-30 2:54 ` Joseph Myers
2015-01-30 6:57 ` Mike Stump
2015-01-30 17:46 ` Joseph Myers
2015-01-30 17:52 ` Mike Stump
2015-01-30 18:06 ` Marek Polacek
2015-01-30 23:48 ` Bernhard Reutner-Fischer
2015-01-30 22:16 ` Mike Stump
2015-02-02 23:22 ` [PATCH, v0] fortran: !GCC$ unroll for DO Bernhard Reutner-Fischer
2015-02-03 8:42 ` Tobias Burnus
2015-02-02 23:22 ` [PATCH, RFC] fortran [was Re: #pragma GCC unroll support] Bernhard Reutner-Fischer
2015-02-03 0:08 ` Mike Stump
2015-05-28 9:56 ` Bernhard Reutner-Fischer
2015-05-28 12:29 ` Mike Stump
2015-11-02 12:18 ` Bernhard Reutner-Fischer
2015-03-05 23:13 ` #pragma GCC unroll support Mike Stump
2015-03-06 1:32 ` Sandra Loosemore
2015-03-06 12:37 ` Bernhard Reutner-Fischer
2015-03-07 1:16 ` Joseph Myers
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=F9073DC4-1F6C-473B-83DA-6D012AB6F08B@comcast.net \
--to=mikestump@comcast.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=joseph@codesourcery.com \
--cc=richard.guenther@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).