public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Martin Jambor <mjambor@suse.cz>
To: Adharsh Kamath <adharshkamathr@gmail.com>, gcc@gcc.gnu.org
Cc: Jakub Jelinek <jakub@redhat.com>
Subject: Re: GSoC 2021 project help
Date: Mon, 21 Dec 2020 23:07:41 +0100	[thread overview]
Message-ID: <ri6lfdqg6du.fsf@suse.cz> (raw)
In-Reply-To: <CAKr9Oczbqmr96x7eCpDkk40WWKk91E8-oKY3OMxGOnr5ZYN9Xg@mail.gmail.com>

Hi Adharsh,

I will be the GSoC organizer for GCC the next year (unless someone else
wants to be).

On Sun, Dec 20 2020, Adharsh Kamath via Gcc wrote:
> Hi everyone
> I came across the list of project ideas that were selected for GSoC 2020
> and I'm interested in contributing to the project regarding the *Implementation
> of OMPD in GCC, libgomp, and GDB. *

> Is this project going to be considered for GSoC 2021 as well?

On one hand, I am very pleased that you are interested in a GCC GSoC
program, on the other, I am worried about the project you picked because
it is very difficult.  We had a student attempting it last year, which
unfortunately failed, and in the process it became painfully clear just
how tough it was for a newcomer.

Moreover, Google has shrunk the duration of GSoC this year, making it
even more difficult to attempt such a big endeavor, and so I was not
planning to keep it in the list of proposed projects for 2021.

Having said that, if you managed to bring about some real progress with
OMPD, it would have a big impact and would indeed be very welcome, so at
least I am not dead set against considering it.  But you'll have to
convince us you really understand what you are attempting.

Do you have some rudimentary knowledge of OpenMP?  Have you looked at
the OMPD part of the standard?  Do you feel you understand what its
goals are?

> I was able to build GCC from source, as specified in the *Before you apply*
> section.

This project would not deal so much with the compiler but mainly with
the run-time OpenMP library libgomp, in the libgomp subdirectory of the
GCC git repository.  At some point you'll have to familiarize yourself
with it, so it might be a good way to start.

You can compile some simple OpenMP program with options
-fopenmp -fdump-tree-optimized
and the generated dump file should show you what the compiler did to the
OpenMP directives and what are the entry points to the run-time library
(for the pragmas used in the program).

> How can I get started with this project? Can I contact the mentor who is
> mentioned in the above project's description regarding this?

I believe you can, in fact I have CCed him on this email already.
Jakub, what are your thoughts?  Can you think of some preliminary work
for Adharsh so that he can get a taste of what he is up to, and so that
we know whether he has a good chance of completing the project?  (And
IMHO completing really means writing something substantial and useful.
The entire OMPD is simply too large, I'm afraid).

Adharsh, I do not want to discourage you.  If you still think you can
succeed after looking into the problem, please do apply, I would love
someone to help with OMPD.  But at the same time I feel I have to
caution you that the project you have picked is a hard one.

Good luck,

Martin

  reply	other threads:[~2020-12-21 22:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-20 13:41 Adharsh Kamath
2020-12-21 22:07 ` Martin Jambor [this message]
2020-12-23 22:31   ` Adharsh Kamath

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=ri6lfdqg6du.fsf@suse.cz \
    --to=mjambor@suse.cz \
    --cc=adharshkamathr@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jakub@redhat.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).