On Tue, Oct 13, 2020 at 07:05:10PM +0100, Kwok Cheung Yeung wrote:
> +* omp_get_supported_active_levels:: Maxiumum number of active levels
> supported
Sorry for not catching it during review, but there is a typo above. Fixed
with patch below, committed to trunk.
> +@node omp_get_supported_active_levels
> +@section @code{omp_get_supported_active_levels} -- Maximum number of active
> regions supported
I also wonder about the different wording between the above two places,
don't you want the same wording as earlier here?
> +@table @asis
> +@item @emph{Description}:
> +This function returns the maximum number of nested, active parallel regions
> +supported by this implementation.
2020-10-14 Jakub Jelinek <ja...@redhat.com>
* libgomp.texi (omp_get_supported_active_levels): Fix a typo.
--- libgomp/libgomp.texi.jj 2020-10-13 22:29:22.215958176 +0200
+++ libgomp/libgomp.texi 2020-10-13 22:29:52.816516414 +0200
@@ -177,7 +177,7 @@ linkage, and do not throw exceptions.
* omp_get_num_threads:: Size of the active team
* omp_get_proc_bind:: Whether theads may be moved between CPUs
* omp_get_schedule:: Obtain the runtime scheduling method
-* omp_get_supported_active_levels:: Maxiumum number of active levels supported
+* omp_get_supported_active_levels:: Maximum number of active levels supported
* omp_get_team_num:: Get team number
* omp_get_team_size:: Number of threads in a team
* omp_get_thread_limit:: Maximum number of threads
Jakub
