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 libgomp/98258] Can't compile programs for both OpenMP (CPU) + OpenACC (GPU)
Date: Mon, 04 Jan 2021 16:52:37 +0000	[thread overview]
Message-ID: <bug-98258-4-gYUon6MaUH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98258-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |amonakov at gcc dot gnu.org,
                   |                            |burnus at gcc dot gnu.org

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The error comes from config/nvptx/mkoffload.c
  if (!(fopenacc ^ fopenmp))
    fatal_error (input_location, "either %<-fopenacc%> or %<-fopenmp%> "
                 "must be set");
I guess this is because in order to compile NVPTX offloading OpenMP code one
needs different Options (e.g. -mgomp ) than for OpenACC code, making NVPTX
offloading incompatible between the two standards.
I think you can use both if you disable nvptx offloading (e.g. through
-foffload= option).

  parent reply	other threads:[~2021-01-04 16:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-13  4:52 [Bug libgomp/98258] New: " mehdi.chinoune at hotmail dot com
2021-01-04 14:26 ` [Bug libgomp/98258] " rguenth at gcc dot gnu.org
2021-01-04 16:43 ` mehdi.chinoune at hotmail dot com
2021-01-04 16:52 ` jakub at gcc dot gnu.org [this message]
2021-01-04 17:34 ` mehdi.chinoune at hotmail dot com
2021-01-04 21:42 ` amonakov at gcc dot gnu.org
2021-01-05  4:34 ` mehdi.chinoune at hotmail dot com
2021-01-05  6:16 ` mehdi.chinoune at hotmail dot com
2021-01-05  7:43 ` amonakov at gcc dot gnu.org
2021-01-05  8:15 ` mehdi.chinoune at hotmail dot com
2021-01-05  8:48 ` amonakov at gcc dot gnu.org
2021-01-05 13:12 ` mehdi.chinoune at hotmail dot com
2021-07-28  8:27 ` mehdi.chinoune at hotmail dot com

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-98258-4-gYUon6MaUH@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).