public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Martin Jambor <mjambor@suse.cz>
Cc: LIU SIYUAN <SLIU019@e.ntu.edu.sg>, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Queries on GSoC project on OMPD interface
Date: Thu, 15 Mar 2018 11:35:00 -0000	[thread overview]
Message-ID: <20180315085913.GQ8577@tucnak> (raw)
In-Reply-To: <ri67eqe4mn3.fsf@suse.cz>

On Wed, Mar 14, 2018 at 06:01:20PM +0100, Martin Jambor wrote:
> Hello Siyuan,
> 
> On Mon, Mar 12 2018, LIU SIYUAN wrote:
> > Dear all,
> >
> > Hi, my name is Siyuan and this is my first time using the GCC mailing list!
> 
> Welcome!

Yeah, welcome.

> For the OMPD task, you will primarily want to look at the OMP run-time
> that is in the libgomp subdirectory (and on the libgomp.exp part of the
> testsuite).  You will probably also want to have a look at how to build
> GDB.
> 
> The OMPD itself is described in the latest TR of the upcoming version of
> the OpenMP standard:
> http://www.openmp.org/wp-content/uploads/openmp-TR6.pdf
> 
> I assume that once you familiarize with the standard and look at how the
> OpenMP run-time is organized (at least roughly), you will want to reach
> out to Jakub (CCed) to figure out how to structure your work.

The task would be to add the libgompd.so.1 library and header files which implement the
APIs in the 4.2 OMPD section of the above spec (and any further changes that
get ratified into upcoming OpenMP 5.0) and any necessary changes on the
libgomp.so.1 side needed for that.  For the latter, it is important to make
sure the changes don't slow the runtime down, or don't slow it down
significantly if there is no other way, and it would be nice to use some
framework like https://infinitynotes.org/wiki/Infinity to communicate
structure offsets, flags, etc. between the libgompd.so.1 and libgomp.so.1,
so that if possible a debugger could bypass the plugin library and e.g. for
performance reasons use the bytecode directly or that one version of the
plugin can deal with slightly different version of the runtime library (e.g.
for the case of running debugger in one platform and gdb server + libgomp on
another one).

	Jakub

      reply	other threads:[~2018-03-15 11:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-12 13:45 #LIU SIYUAN#
2018-03-14 17:01 ` Martin Jambor
2018-03-15 11:35   ` Jakub Jelinek [this message]

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=20180315085913.GQ8577@tucnak \
    --to=jakub@redhat.com \
    --cc=SLIU019@e.ntu.edu.sg \
    --cc=gcc@gcc.gnu.org \
    --cc=mjambor@suse.cz \
    /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).