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-1936] Doc update: -foffload-options= examples + OpenMP in Fortran intrinsic modules Date: Mon, 19 Jun 2023 08:56:34 +0000 (GMT) [thread overview] Message-ID: <20230619085634.9F4533858D32@sourceware.org> (raw) https://gcc.gnu.org/g:e9c1679c350be09cec5354a3d98915c3afe02c87 commit r14-1936-ge9c1679c350be09cec5354a3d98915c3afe02c87 Author: Tobias Burnus <tobias@codesourcery.com> Date: Mon Jun 19 10:24:08 2023 +0200 Doc update: -foffload-options= examples + OpenMP in Fortran intrinsic modules With LTO, the -O.. flags of the host are passed on to the lto compiler, which also includes offloading compilers. Therefore, using --foffload-options=-O3 is misleading as it implies that without the default optimizations are used. Hence, this flags has now been removed from the usage examples. The Fortran documentation lists the content (except for API routines) routines of the intrinsic OpenMP modules OMP_LIB and OMP_LIB_KINDS; this commit adds two missing named constants and links also to the OpenMP 5.1 and 5.2 OpenMP spec for completeness. gcc/ChangeLog: * doc/invoke.texi (-foffload-options): Remove '-O3' from the examples. gcc/fortran/ChangeLog: * intrinsic.texi (OpenMP Modules OMP_LIB and OMP_LIB_KINDS): Also add references to the OpenMP 5.1 and 5.2 spec; add omp_initial_device and omp_invalid_device named constants. Diff: --- gcc/doc/invoke.texi | 2 +- gcc/fortran/intrinsic.texi | 20 ++++++++++++++++---- 2 files changed, 17 insertions(+), 5 deletions(-) diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi index fafdee30f66..215ab0dd05c 100644 --- a/gcc/doc/invoke.texi +++ b/gcc/doc/invoke.texi @@ -2718,7 +2718,7 @@ Typical command lines are @smallexample -foffload-options='-fno-math-errno -ffinite-math-only' -foffload-options=nvptx-none=-latomic --foffload-options=amdgcn-amdhsa=-march=gfx906 -foffload-options=-O3 +-foffload-options=amdgcn-amdhsa=-march=gfx906 @end smallexample @opindex fopenacc diff --git a/gcc/fortran/intrinsic.texi b/gcc/fortran/intrinsic.texi index 5555db227ea..6c7ad03a02c 100644 --- a/gcc/fortran/intrinsic.texi +++ b/gcc/fortran/intrinsic.texi @@ -15247,8 +15247,9 @@ with the following options: @code{-fno-unsafe-math-optimizations @table @asis @item @emph{Standard}: OpenMP Application Program Interface v4.5, -OpenMP Application Program Interface v5.0 (partially supported) and -OpenMP Application Program Interface v5.1 (partially supported). +OpenMP Application Program Interface v5.0 (partially supported), +OpenMP Application Program Interface v5.1 (partially supported) and +OpenMP Application Program Interface v5.2 (partially supported). @end table The OpenMP Fortran runtime library routines are provided both in @@ -15262,9 +15263,13 @@ below. For details refer to the actual @uref{https://www.openmp.org/wp-content/uploads/openmp-4.5.pdf, -OpenMP Application Program Interface v4.5} and +OpenMP Application Program Interface v4.5}, @uref{https://www.openmp.org/wp-content/uploads/OpenMP-API-Specification-5.0.pdf, -OpenMP Application Program Interface v5.0}. +OpenMP Application Program Interface v5.0}, +@uref{https://www.openmp.org/wp-content/uploads/OpenMP-API-Specification-5-1.pdf, +OpenMP Application Program Interface v5.1} and +@uref{https://www.openmp.org/wp-content/uploads/OpenMP-API-Specification-5-2.pdf, +OpenMP Application Program Interface v5.2}. @code{OMP_LIB_KINDS} provides the following scalar default-integer named constants: @@ -15295,6 +15300,13 @@ The following derived type: @item @code{omp_alloctrait} @end table +The following scalar default-integer named constants: +@table @asis +@item @code{omp_initial_device} +@item @code{omp_invalid_device} +@end table + + The following scalar integer named constants of the kind @code{omp_sched_kind}:
reply other threads:[~2023-06-19 8:56 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=20230619085634.9F4533858D32@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).