public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-6077] libgomp: Fix up some typos in libgomp.texi Date: Thu, 16 Feb 2023 11:17:13 +0000 (GMT) [thread overview] Message-ID: <20230216111713.09D363858D33@sourceware.org> (raw) https://gcc.gnu.org/g:0b9bd33d69d0c30330a465e6bad262d90c94d4ea commit r13-6077-g0b9bd33d69d0c30330a465e6bad262d90c94d4ea 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. Diff: --- libgomp/libgomp.texi | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/libgomp/libgomp.texi b/libgomp/libgomp.texi index 698ae330942..1b6358db4dc 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}:
reply other threads:[~2023-02-16 11:17 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=20230216111713.09D363858D33@sourceware.org \ --to=jakub@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).