public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-3259] libgomp: Fix up OpenMP 5.2 feature bullet Date: Wed, 12 Oct 2022 16:49:42 +0000 (GMT) [thread overview] Message-ID: <20221012164942.D9DB93858D38@sourceware.org> (raw) https://gcc.gnu.org/g:caf9db5a7f99fae8b6088328b9b48ee79fa5e5f0 commit r13-3259-gcaf9db5a7f99fae8b6088328b9b48ee79fa5e5f0 Author: Jakub Jelinek <jakub@redhat.com> Date: Wed Oct 12 18:43:58 2022 +0200 libgomp: Fix up OpenMP 5.2 feature bullet The previous bullet correctly mentions 5.2 added for Fortran allocators directive which is a replacement of allocate directive associated with ALLOCATE statement to differentiate it at parse time from allocate directive as declarative one not associated with ALLOCATE statement, but the deprecation bullet talks about non-existing allocator directive. 2022-10-12 Jakub Jelinek <jakub@redhat.com> * libgomp.texi (OpenMP 5.2): Fix up allocator -> allocate directive in deprecation bullet. Diff: --- libgomp/libgomp.texi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libgomp/libgomp.texi b/libgomp/libgomp.texi index 148728ed05f..8d3b9cfb64d 100644 --- a/libgomp/libgomp.texi +++ b/libgomp/libgomp.texi @@ -387,7 +387,7 @@ to address of matching mapped list item per 5.1, Sect. 2.21.7.2 @tab N @tab @item Extended list of directives permitted in Fortran pure procedures @tab N @tab @item New @code{allocators} directive for Fortran @tab N @tab -@item Deprecation of @code{allocator} directive for Fortran +@item Deprecation of @code{allocate} directive for Fortran allocatables/pointers @tab N @tab @item Optional paired @code{end} directive with @code{dispatch} @tab N @tab @item New @code{memspace} and @code{traits} modifiers for @code{uses_allocators}
reply other threads:[~2022-10-12 16:49 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=20221012164942.D9DB93858D38@sourceware.org \ --to=jakub@gcc.gnu.org \ --cc=gcc-cvs@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).