public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Kwok Cheung Yeung <kcy@codesourcery.com>
Cc: Tobias Burnus <tobias@codesourcery.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] openmp: Add support for omp_get_supported_active_levels
Date: Thu, 15 Oct 2020 11:40:21 +0200	[thread overview]
Message-ID: <20201015094021.GX2176@tucnak> (raw)
In-Reply-To: <8a7c1b2f-bd46-d70e-1a5d-ee4f483a9a2f@codesourcery.com>

On Thu, Oct 15, 2020 at 10:38:56AM +0100, Kwok Cheung Yeung wrote:
> Okay to apply this patch?

Ok, thanks.

> commit 3f6f8808f74598e274bfb8245c08a5428ee1b3fd
> Author: Kwok Cheung Yeung <kcy@codesourcery.com>
> Date:   Thu Oct 15 02:32:09 2020 -0700
> 
>     Amend documentation for omp_get_max_active_levels and omp_get_supported_active_levels
>     
>     2020-10-15  Kwok Cheung Yeung  <kcy@codesourcery.com>
>     
>     	libgomp/
>     	* libgomp.texi (omp_get_max_active_levels): Modify description.
>     	(omp_get_supported_active_levels): Make descriptions consistent.
> 
> diff --git a/libgomp/libgomp.texi b/libgomp/libgomp.texi
> index 4a5e56f..7c6d5fd 100644
> --- a/libgomp/libgomp.texi
> +++ b/libgomp/libgomp.texi
> @@ -167,7 +167,7 @@ linkage, and do not throw exceptions.
>  * omp_get_default_device::      Get the default device for target regions
>  * omp_get_dynamic::             Dynamic teams setting
>  * omp_get_level::               Number of parallel regions
> -* omp_get_max_active_levels::   Maximum number of active regions
> +* omp_get_max_active_levels::   Current maximum number of active regions
>  * omp_get_max_task_priority::   Maximum task priority value that can be set
>  * omp_get_max_threads::         Maximum number of threads of parallel region
>  * omp_get_nested::              Nested parallel regions
> @@ -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:: Maximum number of active levels supported
> +* omp_get_supported_active_levels:: Maximum number of active regions 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
> @@ -380,7 +380,7 @@ which enclose the calling call.
>  
>  
>  @node omp_get_max_active_levels
> -@section @code{omp_get_max_active_levels} -- Maximum number of active regions
> +@section @code{omp_get_max_active_levels} -- Current maximum number of active regions
>  @table @asis
>  @item @emph{Description}:
>  This function obtains the maximum allowed number of nested, active parallel regions.


	Jakub


  reply	other threads:[~2020-10-15  9:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-13 18:05 Kwok Cheung Yeung
2020-10-13 18:36 ` Jakub Jelinek
2020-10-13 20:26   ` Kwok Cheung Yeung
2020-10-14  8:20 ` Jakub Jelinek
2020-10-15  9:38   ` Kwok Cheung Yeung
2020-10-15  9:40     ` Jakub Jelinek [this message]
2020-10-20 13:51 David Edelsohn
2020-10-20 13:55 ` Tobias Burnus

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=20201015094021.GX2176@tucnak \
    --to=jakub@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=kcy@codesourcery.com \
    --cc=tobias@codesourcery.com \
    /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: link
Be 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).