public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "LAMOME Julien CS-SI" <julien.lamome-cs-si@irsn.fr>
To: <gcc-help@gcc.gnu.org>
Subject: Automatic Parallelization fail
Date: Thu, 08 Dec 2011 14:47:00 -0000	[thread overview]
Message-ID: <72041471EE7D1540B7ECD771EA430DB7040E3C37@AMESS102.proton.intra.irsn.fr> (raw)

Hi !
I try to use the automatic parellilazion with the last (4.6.2) gcc version. I use this « tuto » http://openwall.info/wiki/internal/gcc-local-build for building gcc and tools.
I compile with :
my-gcc loop.c -o loop -fopenmp -floop-parallelize-all -ftree-parallelize-loops=8 -fdump-tree-parloops-details -lpthread

When I launch my "loop", I have only one processor used.
If I add a "#pragma " directive (for use explicitely OpenMP), I have some processors used.

In test-c-117t.parloops, loop 5 and 7are not noted "loop is not parallel according to graphite", so I think they could be parallelized ?

Thank for your help

                 reply	other threads:[~2011-12-08 14:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=72041471EE7D1540B7ECD771EA430DB7040E3C37@AMESS102.proton.intra.irsn.fr \
    --to=julien.lamome-cs-si@irsn.fr \
    --cc=gcc-help@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).