public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/60997] -fopenmp conflicts with -floop-interchange
Date: Thu, 12 Jun 2014 19:55:00 -0000	[thread overview]
Message-ID: <bug-60997-4-50vl0fkdWr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60997-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60997

--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Also, the compiler really isn't allowed to interchange the !$OMP DO loop
(outermost) with the inner ones, it has different semantics because of the
markup.  The compiler could still interchange the inner two loops if it is
beneficial.  You can also try to use collapse(2) or collapse(3) clause on the
!$OMP DO, then the outermost two or all 3 loops are workshared together.


      parent reply	other threads:[~2014-06-12 19:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-29  9:54 [Bug tree-optimization/60997] New: " dominiq at lps dot ens.fr
2014-04-29 12:11 ` [Bug tree-optimization/60997] " rguenth at gcc dot gnu.org
2014-04-29 13:38 ` dominiq at lps dot ens.fr
2014-04-29 15:24 ` mircea.namolaru at inria dot fr
2014-06-12 18:22 ` dominiq at lps dot ens.fr
2014-06-12 18:58 ` jakub at gcc dot gnu.org
2014-06-12 19:55 ` jakub at gcc dot gnu.org [this message]

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=bug-60997-4-50vl0fkdWr@http.gcc.gnu.org/bugzilla/ \
    --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).