From: Madhu patel <patelmadhu06@gmail.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: gcc@gcc.gnu.org
Subject: Re: GSoC'2023: Separate Host Process Offloading: GCC
Date: Wed, 15 Mar 2023 14:56:22 +0530 [thread overview]
Message-ID: <CABDzTvbKkvwBp=UWNNC3QAvMfB_W5FfodvEwS9b92xLLu4Z+uQ@mail.gmail.com> (raw)
In-Reply-To: <CABDzTvYDtBpNHQbd2Ycp7rtfE5mRezRmOCe=2maSOTm2_T61ug@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1221 bytes --]
Hi Thomas
> (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.)
Thank you for looping folks in; I'm equally interested in both projects,
and it would be great if you can suggest a few tasks that I can take up.
>>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.
Yes, I have built the GCC from scratch on my Linux Machine.
I have written the documentation for the same. And working on understanding
the details of offLoading.
https://www.dropbox.com/scl/fi/ffx7c29f0yfhvbiuvndku/GCC.paper?dl=0&rlkey=76x89xkzz3h41uemor9ksw6sl
> Which specifically?
I've subscribed to this mailing list. gcc@gcc.gnu.org
Can we schedule a meeting to discuss the project's timeline and specific
tasks that I can take on?
Please let me know your availability, as my time zone is IST. I have
developed an understanding of offloading.
~Madhu
prev parent reply other threads:[~2023-03-15 9:26 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
2023-03-13 20:43 ` Thomas Schwinge
[not found] ` <CABDzTvYDtBpNHQbd2Ycp7rtfE5mRezRmOCe=2maSOTm2_T61ug@mail.gmail.com>
2023-03-15 9:26 ` Madhu patel [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='CABDzTvbKkvwBp=UWNNC3QAvMfB_W5FfodvEwS9b92xLLu4Z+uQ@mail.gmail.com' \
--to=patelmadhu06@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=thomas@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).