public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Tobias Burnus <burnus@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/devel/omp/gcc-12] libgomp: Fix up OpenMP 5.2 feature bullet
Date: Mon, 17 Oct 2022 15:02:03 +0000 (GMT)	[thread overview]
Message-ID: <20221017150204.A5DD03858406@sourceware.org> (raw)

https://gcc.gnu.org/g:452bb7db311b5a4987558b7fbfc450768a0e167f

commit 452bb7db311b5a4987558b7fbfc450768a0e167f
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Mon Oct 17 16:57:09 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.
    
    (cherry picked from commit caf9db5a7f99fae8b6088328b9b48ee79fa5e5f0)

Diff:
---
 libgomp/ChangeLog.omp | 8 ++++++++
 libgomp/libgomp.texi  | 2 +-
 2 files changed, 9 insertions(+), 1 deletion(-)

diff --git a/libgomp/ChangeLog.omp b/libgomp/ChangeLog.omp
index 23ec0e9de62..debb77b2150 100644
--- a/libgomp/ChangeLog.omp
+++ b/libgomp/ChangeLog.omp
@@ -1,3 +1,11 @@
+2022-10-17  Tobias Burnus  <tobias@codesourcery.com>
+
+	Backport from mainline:
+	2022-10-12  Jakub Jelinek  <jakub@redhat.com>
+
+	* libgomp.texi (OpenMP 5.2): Fix up allocator -> allocate directive
+	in deprecation bullet.
+
 2022-10-17  Tobias Burnus  <tobias@codesourcery.com>
 
 	Backport from mainline:
diff --git a/libgomp/libgomp.texi b/libgomp/libgomp.texi
index e9edeff0bba..d0be6058067 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-17 15:02 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=20221017150204.A5DD03858406@sourceware.org \
    --to=burnus@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: 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).