public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Aldy Hernandez <aldyh@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [gomp4.1] document more structures in libgomp.h
Date: Fri, 28 Aug 2015 14:46:00 -0000	[thread overview]
Message-ID: <20150828143153.GN9425@tucnak.redhat.com> (raw)
In-Reply-To: <55E06E7A.5000002@redhat.com>

On Fri, Aug 28, 2015 at 07:21:46AM -0700, Aldy Hernandez wrote:
>     	* libgomp.h: Document gomp_task_depend_entry, gomp_task,
>     	gomp_taskgroup.
>     	*task.c (gomp_task_run_pre): Add comments.

Missing space before task.c.

> --- a/libgomp/libgomp.h
> +++ b/libgomp/libgomp.h
> @@ -279,9 +279,11 @@ struct htab;
>  
>  struct gomp_task_depend_entry
>  {
> +  /* Address of dependency.  */
>    void *addr;
>    struct gomp_task_depend_entry *next;
>    struct gomp_task_depend_entry *prev;
> +  /* Task that provides the depdency in ADDR.  */

Typo.

>    struct gomp_task *task;
>    /* Depend entry is of type "IN".  */
>    bool is_in;
> @@ -312,10 +314,14 @@ struct gomp_taskwait
>  struct gomp_task
>  {
>    struct gomp_task *parent;
> +  /* Children of this task.  Siblings are chained by
> +     NEXT/PREV_CHILD fields below.  */

I think it would be better to say here that it is a circular list,
and how the siblings are ordered in the circular list.

>  struct gomp_taskgroup
>  {
>    struct gomp_taskgroup *prev;
> +  /* List of tasks that belong in this taskgroup.  Tasks are chained
> +     by next/prev_taskgroup within the gomp_task.  */

Again, perhaps mention also that it is a circular list and how the items of
the circular list are sorted.

> +  /* Scheduled tasks.  Chain fields are next/prev_queue within a
> +     gomp_task.  */

Similarly.
>    struct gomp_task *task_queue;


	Jakub

  reply	other threads:[~2015-08-28 14:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-28 14:32 Aldy Hernandez
2015-08-28 14:46 ` Jakub Jelinek [this message]
2015-08-28 15:56   ` Aldy Hernandez
2015-08-28 15:59     ` Jakub Jelinek

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=20150828143153.GN9425@tucnak.redhat.com \
    --to=jakub@redhat.com \
    --cc=aldyh@redhat.com \
    --cc=gcc-patches@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: 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).