public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Thomas Schwinge <thomas@codesourcery.com>
To: Lewis Braley <lewis0112@gmail.com>
Cc: <gcc-help@gcc.gnu.org>
Subject: Re: OpenACC parallelization
Date: Wed, 15 Apr 2020 13:34:41 +0200	[thread overview]
Message-ID: <87v9m17zji.fsf@euler.schwinge.homeip.net> (raw)
In-Reply-To: <CALUo15D4Cb+B87ybF2YLiZV5RCzx=CytRD68MpxL4QS-uPtV9w@mail.gmail.com>

Hi!

On 2020-04-14T09:40:06+0100, Lewis Braley via Gcc-help <gcc-help@gcc.gnu.org> wrote:
> I have been trying to use OpenACC to allow for cpu-based loop
> parallelization in GCC, however I cannot seem to get it working in either C
> or C++.>

Thanks for your interest!

> The PGI C++ compiler will successfully compile and run parallel
> code.
>
> This stack overflow post has more details:
> https://stackoverflow.com/questions/61017223/compiling-c-openacc-parallel-cpu-code-using-gcc-g

I answered on there, <https://stackoverflow.com/a/61227622/664214>:

| It's not yet supported in GCC to use OpenACC to schedule parallel loops onto multicore CPUs. Using OpenMP works for that, of course, and you can have code with mixed OpenACC (for GPU offloading, as already present in your code) and OpenMP directives (for CPU parallelization, not yet present in your code), so that the respective mechanism will be used depending on whether compiling with `-fopenacc` vs. `-fopenmp`.
|
| Like PGI are doing, it certainly can be supported in GCC; we'll certainly be able to implement that, but it has not yet been scheduled, has not yet been funded for GCC.


Grüße
 Thomas
-----------------
Mentor Graphics (Deutschland) GmbH, Arnulfstraße 201, 80634 München / Germany
Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung, Alexander Walter

      reply	other threads:[~2020-04-15 11:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-14  8:40 Lewis Braley
2020-04-15 11:34 ` Thomas Schwinge [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=87v9m17zji.fsf@euler.schwinge.homeip.net \
    --to=thomas@codesourcery.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=lewis0112@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).