public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/108558] OpenMP/Fortran 'has_device_addr' clause getting lost? Date: Thu, 26 Jan 2023 13:46:53 +0000 [thread overview] Message-ID: <bug-108558-4-bHiMB2o0HY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108558-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108558 --- Comment #2 from Thomas Schwinge <tschwinge at gcc dot gnu.org> --- (In reply to Tobias Burnus from comment #1) > I bet that this is a problem of 'gfc_split_omp_clauses': [...] Heh, so indeed as I suspected: (In reply to myself from comment #0) > (Decomposed combined construct. Is that perhaps where the problem lies?) :-) With your patch (thanks!) applied, I do get what I suspect are the expected changes: 'pr.f90.005t.original': - #pragma omp target + #pragma omp target has_device_addr(a) has_device_addr(b) 'pr.f90.006t.gimple': - #pragma omp target num_teams(0) thread_limit(0) firstprivate(m) map(tofrom:*b [len: D.4283][implicit]) map(alloc:b [pointer assign, bias: 0]) map(tofrom:*a [len: D.4280][implicit]) map(alloc:a [pointer assign, bias: 0]) + #pragma omp target num_teams(0) thread_limit(0) has_device_addr(a) has_device_addr(b) firstprivate(D.4283) firstprivate(D.4280) firstprivate(m) ..., and my original test case behaves as expected; OpenMP/Fortran 'has_device_addr' works.
next prev parent reply other threads:[~2023-01-26 13:46 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-26 12:02 [Bug fortran/108558] New: " tschwinge at gcc dot gnu.org 2023-01-26 12:36 ` [Bug fortran/108558] " burnus at gcc dot gnu.org 2023-01-26 13:46 ` tschwinge at gcc dot gnu.org [this message] 2023-01-27 10:34 ` cvs-commit at gcc dot gnu.org 2023-01-27 10:48 ` burnus at gcc dot gnu.org 2023-01-30 8:57 ` cvs-commit at gcc dot gnu.org 2023-01-30 9:22 ` 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-108558-4-bHiMB2o0HY@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).