[gcc r11-10714] libgomp: Fix up some typos in libgomp.texi
Jakub Jelinek
jakub@gcc.gnu.org
Tue May 2 20:14:55 GMT 2023
https://gcc.gnu.org/g:8dafd18e2b0098ef5b48232df5ba2874443673e4
commit r11-10714-g8dafd18e2b0098ef5b48232df5ba2874443673e4
Author: Jakub Jelinek <jakub@redhat.com>
Date: Thu Feb 16 12:15:03 2023 +0100
libgomp: Fix up some typos in libgomp.texi
I decided to check for repeated the the in libgomp and noticed
there are several occurrences of a typo theads rather than threads
in libgomp.texi.
2023-02-16 Jakub Jelinek <jakub@redhat.com>
* libgomp.texi: Fix typos - theads -> threads.
(cherry picked from commit 0b9bd33d69d0c30330a465e6bad262d90c94d4ea)
Diff:
---
libgomp/libgomp.texi | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/libgomp/libgomp.texi b/libgomp/libgomp.texi
index 2c1f1b5968b..ec86f44a8ea 100644
--- a/libgomp/libgomp.texi
+++ b/libgomp/libgomp.texi
@@ -176,7 +176,7 @@ linkage, and do not throw exceptions.
* omp_get_num_procs:: Number of processors online
* omp_get_num_teams:: Number of teams
* omp_get_num_threads:: Size of the active team
-* omp_get_proc_bind:: Whether theads may be moved between CPUs
+* omp_get_proc_bind:: Whether threads may be moved between CPUs
* omp_get_schedule:: Obtain the runtime scheduling method
* omp_get_supported_active_levels:: Maximum number of active regions supported
* omp_get_team_num:: Get team number
@@ -626,7 +626,7 @@ one thread per CPU online is used.
@node omp_get_proc_bind
-@section @code{omp_get_proc_bind} -- Whether theads may be moved between CPUs
+@section @code{omp_get_proc_bind} -- Whether threads may be moved between CPUs
@table @asis
@item @emph{Description}:
This functions returns the currently active thread affinity policy, which is
@@ -1455,8 +1455,8 @@ beginning with @env{GOMP_} are GNU extensions.
* OMP_MAX_TASK_PRIORITY:: Set the maximum task priority value
* OMP_NESTED:: Nested parallel regions
* OMP_NUM_THREADS:: Specifies the number of threads to use
-* OMP_PROC_BIND:: Whether theads may be moved between CPUs
-* OMP_PLACES:: Specifies on which CPUs the theads should be placed
+* OMP_PROC_BIND:: Whether threads may be moved between CPUs
+* OMP_PLACES:: Specifies on which CPUs the threads should be placed
* OMP_STACKSIZE:: Set default thread stack size
* OMP_SCHEDULE:: How threads are scheduled
* OMP_TARGET_OFFLOAD:: Controls offloading behaviour
@@ -1634,12 +1634,12 @@ nesting by default. If undefined one thread per CPU is used.
@node OMP_PROC_BIND
-@section @env{OMP_PROC_BIND} -- Whether theads may be moved between CPUs
+@section @env{OMP_PROC_BIND} -- Whether threads may be moved between CPUs
@cindex Environment Variable
@table @asis
@item @emph{Description}:
Specifies whether threads may be moved between processors. If set to
-@code{TRUE}, OpenMP theads should not be moved; if set to @code{FALSE}
+@code{TRUE}, OpenMP threads should not be moved; if set to @code{FALSE}
they may be moved. Alternatively, a comma separated list with the
values @code{MASTER}, @code{CLOSE} and @code{SPREAD} can be used to specify
the thread affinity policy for the corresponding nesting level. With
@@ -1663,7 +1663,7 @@ When undefined, @env{OMP_PROC_BIND} defaults to @code{TRUE} when
@node OMP_PLACES
-@section @env{OMP_PLACES} -- Specifies on which CPUs the theads should be placed
+@section @env{OMP_PLACES} -- Specifies on which CPUs the threads should be placed
@cindex Environment Variable
@table @asis
@item @emph{Description}:
More information about the Gcc-cvs
mailing list