From: Mohamed Atef <mohamedatef1698@gmail.com>
To: gcc-patches@gcc.gnu.org, Jakub Jelinek <jakub@redhat.com>,
Mohamed Sayed <mohamedsayed22198@gmail.com>,
ahmedsayedmousse@gmail.com, youssef.magdy.775@gmail.com,
aya.nashaat99@gmail.com
Subject: Re: [PATCH] libgompd: Fix sizes in OMPD support and add local ICVs finctions.
Date: Wed, 15 Jun 2022 11:55:28 +0200 [thread overview]
Message-ID: <CAPFh8NJoDDc2m5n9VvoMAiygBR+wHhwah3YC=CUMbXm5xZKOmA@mail.gmail.com> (raw)
In-Reply-To: <CAPFh8N+4YqVD2sk7H33mT7YdUT6Lzfdhz8Z0o_QbW9UObiNRzQ@mail.gmail.com>
Ping
في الجمعة، ١٠ يونيو، ٢٠٢٢ ٥:٥٦ م Mohamed Atef <mohamedatef1698@gmail.com>
كتب:
>
> libgomp/ChangeLog
>
> 2022-06-10 Mohamed Atef <mohamedatef1698@gmail.com>
>
> * ompd-helper.h (DEREFERENCE, ACCESS_VALUE): New macros.
> * ompd-helper.c (gompd_get_nthread, gompd_get_thread_limit,
> gomp_get_run_shed, gompd_get_run_sched_chunk_size,
> gompd_get_default_device, gompd_get_dynamic,
> gompd_get_max_active_levels, gompd_get_proc_bind,
> gompd_is_final, gompd_is_implicit, gompd_get_team_size): defined.
> * ompd-icv.c (ompd_get_icv_from_scope): call the previous fincions,
> thread_handle, task_handle and parallel handle: New variable.
> Fix format in ashandle definition.
> * ompd-init.c: call GET_VALUE with sizeof_short for gompd_state.
> * ompd-support.h (gompd_state): size of short instead of long.
> (GOMPD_FOREACH_ACCESS): Add
> gompd_access (gomp_task, kind)
> gompd_access (gomp_task, final_task)
> gompd_access (gomp_team, nthreads)
> * ompd-support.c: Define
> gompd_get_offset
> gompd_get_sizeof_member
> gompd_get_size.
> (gompd_load): Remove gompd_init_access,
> gompd_init_sizeof_members, gompd_init_sizes
> define gompd_access_gomp_thread_handle with __UINT16_TYPE__.
>
>
next prev parent reply other threads:[~2022-06-15 9:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 15:56 Mohamed Atef
2022-06-15 9:55 ` Mohamed Atef [this message]
2022-06-16 12:22 ` Jakub Jelinek
2022-06-16 23:20 Mohamed Atef
2022-06-20 7:31 ` Jakub Jelinek
2022-06-22 2:17 ` Mohamed Atef
2022-06-22 7:55 ` 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='CAPFh8NJoDDc2m5n9VvoMAiygBR+wHhwah3YC=CUMbXm5xZKOmA@mail.gmail.com' \
--to=mohamedatef1698@gmail.com \
--cc=ahmedsayedmousse@gmail.com \
--cc=aya.nashaat99@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=mohamedsayed22198@gmail.com \
--cc=youssef.magdy.775@gmail.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).