public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Thomas Schwinge <thomas@codesourcery.com>
To: Madhu patel <patelmadhu06@gmail.com>
Cc: <gcc@gcc.gnu.org>
Subject: Re: GSoC'2023: Separate Host Process Offloading: GCC
Date: Mon, 13 Mar 2023 21:37:24 +0100	[thread overview]
Message-ID: <87o7owwfp7.fsf@euler.schwinge.homeip.net> (raw)
In-Reply-To: <CABDzTvYzRrnsXty_m6dKfr113CE1V7GJEaJ+CiRofbZxfYNNYw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 262 bytes --]

-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955

[-- Attachment #2: Type: message/rfc822, Size: 4757 bytes --]

[-- Attachment #2.1.1: Type: text/plain, Size: 1865 bytes --]

Hi Madhu!

(As you've sent your equally worded
"GSoC'2023: Bypass assembler when generating LTO object files: GCC" email
to <gcc@gcc.gnu.org>, let me also Cc my reply here to that list, so that
others may contribute, too.)


On 2023-03-09T01:36:02+0530, Madhu patel <patelmadhu06@gmail.com> wrote:
> I'm interested in working on the project `Separate Host Process Offloading`
> in the GCC organization through GSoC'2023.

Great, and welcome to GCC!  :-)

> Please suggest a few initial tasks I can work on during the application
> period and attach them to my application.

Building GCC and producing test results would be one obvious first task,
have you worked on that already?
<https://gcc.gnu.org/wiki/#Getting_Started_with_GCC_Development> has some
pointers to get started.  If you have specific questions, we're happy to
help, of course.

Then, get familiar with the basic concepts of code offloading in GCC.
<https://gcc.gnu.org/wiki/Offloading> is the best (only?) we have,
unfortunately, and it's somewhat out of date, so beware, sorry.  Looking
at existing libgomp plugins may help: 'libgomp/plugin/plugin-*.c', and
actually also the very simple 'libgomp/oacc-host.c'.  That's essentially
the API you need to care about (for OpenACC; but OpenMP 'target' also
won't require much more, for a start).

Make some thoughts (or actual experiments) about how we could
use/implement a separate host process for code offloading.

> I have already prepared a
> timeline/planner, great if you could have a look at it and suggest any
> enhancements.

That wasn't attached to or referred to in your email?

> Additionally, I have signed in to the mailing lists, and IRCs
> and done the initial tasks as described on the project page [1]
> <https://gcc.gnu.org/wiki/SummerOfCode>.

Which specifically?


Grüße
 Thomas

[-- Attachment #2.1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 694 bytes --]

       reply	other threads:[~2023-03-13 20:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CABDzTvYzRrnsXty_m6dKfr113CE1V7GJEaJ+CiRofbZxfYNNYw@mail.gmail.com>
2023-03-13 20:37 ` Thomas Schwinge [this message]
2023-03-13 20:43   ` Thomas Schwinge
     [not found]     ` <CABDzTvYDtBpNHQbd2Ycp7rtfE5mRezRmOCe=2maSOTm2_T61ug@mail.gmail.com>
2023-03-15  9:26       ` Madhu patel

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=87o7owwfp7.fsf@euler.schwinge.homeip.net \
    --to=thomas@codesourcery.com \
    --cc=gcc@gcc.gnu.org \
    --cc=patelmadhu06@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).