public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/105640] New: [OpenMP] Context selectors missing for PowerPC
Date: Wed, 18 May 2022 06:32:50 +0000	[thread overview]
Message-ID: <bug-105640-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 105640
           Summary: [OpenMP] Context selectors missing for PowerPC
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Keywords: openmp
          Severity: normal
          Priority: P3
         Component: middle-end
          Assignee: unassigned at gcc dot gnu.org
          Reporter: burnus at gcc dot gnu.org
                CC: jakub at gcc dot gnu.org
  Target Milestone: ---
            Target: powerpc64le,powerpc

Looking at https://gcc.gnu.org/onlinedocs/libgomp/OpenMP-Context-Selectors.html
, I realized that we do now have OpenMP context selectors for PowerPC, which is
somewhat widely used with HPC and offloading and, thus, a relevant omission.

I think something like:
arch = powerpc, powerpc64, powerpc64le, rs64
  ?
kind = cpu
isa = ?
  maybe all values of RS6000_CPU (in rs6000-cpus.def)  excluding or not the
ones from arch
  = documentation wise, -mcpu= w/o 'native' (and possibly the values from arch)

Any other ISA flag?
https://gcc.gnu.org/onlinedocs/gcc/RS_002f6000-and-PowerPC-Options.html

Namely:
* TARGET_OMP_DEVICE_KIND_ARCH_ISA needs to be defined +
   associated rs6000_omp_device_kind_arch_isa be created
* t-omp-device be created
* libgomp.texi updated (cf. link above)
* a test to – or eqiuvalent:
    gcc/testsuite/c-c++-common/gomp/declare-variant-11.c

             reply	other threads:[~2022-05-18  6:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-18  6:32 burnus at gcc dot gnu.org [this message]
2022-05-18  6:38 ` [Bug target/105640] " jakub at gcc dot gnu.org
2022-05-18  6:40 ` jakub at gcc dot gnu.org
2022-05-18  6:51 ` jakub at gcc dot gnu.org
2022-05-18  7:05 ` jakub at gcc dot gnu.org
2022-05-18 10:02 ` burnus at gcc dot gnu.org

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