public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Tobias Burnus <tobias@codesourcery.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [Patch] libgomp: Handle OpenMP's reverse offloads
Date: Sat, 10 Dec 2022 09:28:10 +0100	[thread overview]
Message-ID: <Y5RDGqfBzrzOM6H7@tucnak> (raw)
In-Reply-To: <f28e745b-21f4-da7c-d298-e82a3f41bc73@codesourcery.com>

On Sat, Dec 10, 2022 at 09:11:24AM +0100, Tobias Burnus wrote:
> It is used as 'typedef struct reverse_splay_tree_node_s *reverse_splay_tree_node;' in
> 
> struct target_mem_desc {
> ....
>   reverse_splay_tree_node rev_array;
> }
> 
> but also as
> 
> struct gomp_device_descr
> {
>   ...
>   struct reverse_splay_tree_s mem_map_rev;
> }
> 
> The latter is
> 
> struct reverse_splay_tree_key_s {
>   /* Address of the device object.  */
>   uint64_t dev;
>   splay_tree_key k;
> };
> 
> which in turn needs 'splay_tree_key'.
> 
> Thus, I could either commit it as is – or turn the latter also
> into a pointer and malloc it. Currently, it is accessed as
> mem_map.k.root = NULL for init and later through the splay-tree
> functions indirectly.
> 
> Thoughts?
> 
> Unless there are further comments, I will later commit it as is.

Ok; just wanted to save compile time by not including too much for all the
other files...

	Jakub


  reply	other threads:[~2022-12-10  8:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-06  7:45 Tobias Burnus
2022-12-07  8:08 ` [Patch] libgomp.texi: Reverse-offload updates (was: [Patch] libgomp: Handle OpenMP's reverse offloads) Tobias Burnus
2022-12-10  8:18   ` Tobias Burnus
2023-01-31 12:21     ` Jakub Jelinek
2022-12-09 14:44 ` [Patch] libgomp: Handle OpenMP's reverse offloads Jakub Jelinek
2022-12-10  8:11   ` Tobias Burnus
2022-12-10  8:28     ` Jakub Jelinek [this message]
2022-12-15 17:34 ` Thomas Schwinge
2022-12-15 17:49   ` Jakub Jelinek
2022-12-15 19:42   ` Tobias Burnus
2022-12-15 20:13     ` 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=Y5RDGqfBzrzOM6H7@tucnak \
    --to=jakub@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --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).