From 2e3327d635d261df923f60f7d21e47ff895cd2df Mon Sep 17 00:00:00 2001 From: Jakub Jelinek Date: Thu, 16 Feb 2023 12:33:03 +0100 Subject: [PATCH] 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 * libgomp.texi: Fix typos - theads -> threads. (cherry picked from commit 0b9bd33d69d0c30330a465e6bad262d90c94d4ea) --- libgomp/ChangeLog.omp | 7 +++++++ libgomp/libgomp.texi | 14 +++++++------- 2 files changed, 14 insertions(+), 7 deletions(-) diff --git a/libgomp/ChangeLog.omp b/libgomp/ChangeLog.omp index 5be77242a417..af31412a0c6f 100644 --- a/libgomp/ChangeLog.omp +++ b/libgomp/ChangeLog.omp @@ -1,3 +1,10 @@ +2023-02-16 Tobias Burnus + + Backported from master: + 2023-02-16 Jakub Jelinek + + * libgomp.texi: Fix typos - theads -> threads. + 2023-02-16 Tobias Burnus Backported from master: diff --git a/libgomp/libgomp.texi b/libgomp/libgomp.texi index 1ac7646dbcb3..288e0b3a8eaa 100644 --- a/libgomp/libgomp.texi +++ b/libgomp/libgomp.texi @@ -524,7 +524,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 @@ -1031,7 +1031,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 @@ -1945,8 +1945,8 @@ beginning with @env{GOMP_} are GNU extensions. * OMP_NESTED:: Nested parallel regions * OMP_NUM_TEAMS:: Specifies the number of teams to use by teams region * 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 @@ -2144,12 +2144,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{PRIMARY}, @code{MASTER}, @code{CLOSE} and @code{SPREAD} can be used to specify the thread affinity policy for the corresponding nesting @@ -2174,7 +2174,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}: -- 2.47.2