From: Mike Stump <mikestump@comcast.net>
To: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, gfortran <fortran@gcc.gnu.org>
Subject: Re: [PATCH, RFC] fortran [was Re: #pragma GCC unroll support]
Date: Thu, 28 May 2015 12:29:00 -0000 [thread overview]
Message-ID: <D7456A9B-4487-4218-8072-DE21D46426E0@comcast.net> (raw)
In-Reply-To: <CAC1BbcQqXQgVP=TPFniTb-ELyidGP7M_Gind8+Br-p2dNqsv+A@mail.gmail.com>
On May 28, 2015, at 2:02 AM, Bernhard Reutner-Fischer <rep.dot.nop@gmail.com> wrote:
>
> Does anybody have a better suggestion?
>
> directive not at the start of a loop at %C
> directive not followed by a loop at %C
I prefer either of these. I have a slight preference for the first.
> Mike, did you tweak the one or two things you got from the reviews
> yet?
Nope.
> ISTM your main patch was not OKed yet nor installed.
Been busy with work. I’ll come back and address the nits that people pointed out and see if I can ping it some more and try and get the C++ bits reviewed.
next prev parent reply other threads:[~2015-05-28 12:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 21:51 #pragma GCC unroll support 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
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, 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 [this message]
2015-11-02 12:18 ` Bernhard Reutner-Fischer
2015-02-02 23:22 ` [PATCH, v0] fortran: !GCC$ unroll for DO Bernhard Reutner-Fischer
2015-02-03 8:42 ` Tobias Burnus
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=D7456A9B-4487-4218-8072-DE21D46426E0@comcast.net \
--to=mikestump@comcast.net \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=rep.dot.nop@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).