From: Tim Prince <n8tm@aol.com>
To: fortran@gcc.gnu.org
Subject: Re: Loop Vectorization
Date: Mon, 20 Jun 2016 07:53:00 -0000 [thread overview]
Message-ID: <c5afc8f1-9771-e1d6-5554-8936ec97ad97@aol.com> (raw)
In-Reply-To: <57678924.7050807@net-b.de>
On 6/20/2016 2:11 AM, Tobias Burnus wrote:
> Hello,
>
> sdcycling wrote:
>> I am using gfortran to build a finite-difference code. How do I tell
>> whether a do loop is being vectorized?
> Try the -fopt-info-... options of GCC, in particular
> -fopt-info-vec-optimized
>
>> Also, how do I use compiler directives in gfortran to indicate that a
>> do loop does not have any data dependencies?
>
> Not as directive, but using Fortran's "DO CONCURRENT" instead of a
> normal DO will imply this.
>
!$ omp simd may be useful, if your objective is simd vectorization.
--
Tim Prince
next prev parent reply other threads:[~2016-06-20 7:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 3:06 sdcycling
2016-06-20 6:11 ` Tobias Burnus
2016-06-20 7:53 ` Tim Prince [this message]
[not found] ` <8vtq1t00B2qVqVd01vtrfL>
2016-06-20 15:04 ` sdcycling
2016-06-20 15:56 ` Tim Prince
2016-06-20 19:06 ` Tobias Burnus
[not found] <93wB1t00W2qVqVd013wCG6>
2016-06-20 18:46 ` sdcycling
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=c5afc8f1-9771-e1d6-5554-8936ec97ad97@aol.com \
--to=n8tm@aol.com \
--cc=fortran@gcc.gnu.org \
--cc=tprince@computer.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).