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 target/105602] New: [OpenMP][gcn] — Support multiple arch in gcc/config/gcn/t-omp-device? Add 'amdgcn' (additionally to/instead of 'amd') Date: Sat, 14 May 2022 09:16:46 +0000 [thread overview] Message-ID: <bug-105602-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105602 Bug ID: 105602 Summary: [OpenMP][gcn] — Support multiple arch in gcc/config/gcn/t-omp-device? Add 'amdgcn' (additionally to/instead of 'amd') Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: burnus at gcc dot gnu.org CC: ams at gcc dot gnu.org, jakub at gcc dot gnu.org Target Milestone: --- I note that GCC has in gcc/config/gcn/t-omp-device: echo kind: gpu > $@ echo arch: gcn >> $@ echo isa: fiji gfx900 gfx906 gfx908 >> $@ That is, GCC supports as context selector: match(construct={target},device={arch(gcn)}) In contrast, llvm has, e.g. in clang/lib/Headers/openmp_wrappers/cmath: #pragma omp begin declare variant match(device = {arch(amdgcn)}) Thus: LLVM uses 'amdgcn'. Expected: arch = 'amdgcn' (also) works in GCC for better compatibility. I did not find a documentation and I think either variant is fine – albeit 'amdgcn' seems to be more natural.
next reply other threads:[~2022-05-14 9:16 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-14 9:16 burnus at gcc dot gnu.org [this message] 2022-05-17 13:54 ` [Bug target/105602] " cvs-commit at gcc dot gnu.org 2022-05-17 13:57 ` 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-105602-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: linkBe 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).