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/109998] New: [OpenMP] TR12/5.0/5.1 - permit structure elements with '!$OMP ALLOCATORS' (and !$OMP ALLOCATE)
Date: Fri, 26 May 2023 19:00:04 +0000	[thread overview]
Message-ID: <bug-109998-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 109998
           Summary: [OpenMP] TR12/5.0/5.1 - permit structure elements with
                    '!$OMP ALLOCATORS' (and !$OMP ALLOCATE)
           Product: gcc
           Version: 13.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: ---

Cf. r14-1301-gd64e8e1224708e7f5b87c531aeb26f1ed07f91ff and in particular
in openmp.cc the comment:

   Note that the executable ALLOCATE directive permits structure elements only
   in OpenMP 5.0 and 5.1 but not longer in 5.2.  See also the comment on the
   'omp allocators' directive below. The accidental change was reverted for
   OpenMP TR12, permitting them again. See also gfc_match_omp_allocators.

   Hence, structure elements are rejected for now, also to make resolving
   OMP_LIST_ALLOCATE simpler (check for duplicates, same symbol in
   Fortran allocate stmt).  TODO: Permit structure elements.


EXPECTED: What the TODO says.


For TR12 (OpenMP Spec Issue 3437), the description in the "allocators
directive" section was changed to state:

"The list items that appear in an *allocate* clause may include structure
elements."

(It does not talk about the *allocate* directive any more as TR11/TR12/6.0
removed deprecated features.)

                 reply	other threads:[~2023-05-26 19:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-109998-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).