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 fortran/114283] New: [OpenMP] Dummy procedures/proc pointers and 'defaultmap', 'default', 'firstprivate' etc. Date: Fri, 08 Mar 2024 13:00:30 +0000 [thread overview] Message-ID: <bug-114283-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114283 Bug ID: 114283 Summary: [OpenMP] Dummy procedures/proc pointers and 'defaultmap', 'default', 'firstprivate' etc. Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: openmp Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: burnus at gcc dot gnu.org Target Milestone: --- See also OpenMP specification Issue #3823 [and slightly related PR 114282]. There are two cases: (A) Dummy procedures IMHO those aren't variables and gfortran also rejects them when used in firstprivate, map, shared etc. ("Object 'f1' is not a variable"). However, gfortran does complain with 'default(none)': Error: 'f1' not specified in enclosing 'target' Note: 'default(none)' does not diagnose it. EXPECTED: There is no diagnosis for 'defaultmap(none)'. (B) Procedure pointers Here it is unclear whether it should be regarded as variable or not; gfortran treats those as variables. Depends on OpenMP specification Issue #3823. It seems as if handling it as variable, but using 'firstprivate' as default for implicit mapping makes most sense. – But also treating it as non-variable would make sense.
next reply other threads:[~2024-03-08 13:00 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-08 13:00 burnus at gcc dot gnu.org [this message] 2024-03-13 8:58 ` [Bug fortran/114283] " cvs-commit 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-114283-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).