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 r14-4779] omp_lib.f90.in: Deprecate omp_lock_hint_* for OpenMP 5.0 Date: Fri, 20 Oct 2023 08:57:31 +0000 (GMT) [thread overview] Message-ID: <20231020085731.C025D3858D1E@sourceware.org> (raw) https://gcc.gnu.org/g:5f71e002f8881c8176efa54f83615d2270152e75 commit r14-4779-g5f71e002f8881c8176efa54f83615d2270152e75 Author: Tobias Burnus <tobias@codesourcery.com> Date: Fri Oct 20 10:56:39 2023 +0200 omp_lib.f90.in: Deprecate omp_lock_hint_* for OpenMP 5.0 The omp_lock_hint_* parameters were deprecated in favor of omp_sync_hint_*. While omp.h contained deprecation markers for those, the omp_lib module only contained them for omp_{g,s}_nested. Note: The -Wdeprecated-declarations warning will only become active once openmp_version / _OPENMP is bumped from 201511 (4.5) to 201811 (5.0). libgomp/ChangeLog: * omp_lib.f90.in: Tag omp_lock_hint_* as being deprecated when _OPENMP >= 201811. Diff: --- libgomp/omp_lib.f90.in | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/libgomp/omp_lib.f90.in b/libgomp/omp_lib.f90.in index e45152712529..755c0bf16ec9 100644 --- a/libgomp/omp_lib.f90.in +++ b/libgomp/omp_lib.f90.in @@ -904,6 +904,10 @@ #if _OPENMP >= 201811 !GCC$ ATTRIBUTES DEPRECATED :: omp_get_nested, omp_set_nested +!GCC$ ATTRIBUTES DEPRECATED :: omp_lock_hint_kind, omp_lock_hint_none +!GCC$ ATTRIBUTES DEPRECATED :: omp_lock_hint_uncontended, omp_lock_hint_contended +!GCC$ ATTRIBUTES DEPRECATED :: omp_lock_hint_nonspeculative +!GCC$ ATTRIBUTES DEPRECATED :: omp_lock_hint_speculative #endif #if _OPENMP >= 202011
reply other threads:[~2023-10-20 8:57 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=20231020085731.C025D3858D1E@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: 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).