From: Rishi Raj <rishiraj45035@gmail.com>
To: mjambor@suse.cz, Jan Hubicka <hubicka@ucw.cz>, gcc@gcc.gnu.org
Subject: [GSOC] Submission of draft proposal for Bypass assembler when generating LTO object files
Date: Tue, 4 Apr 2023 06:05:26 +0530 [thread overview]
Message-ID: <CA+1a67PX3TKHXJryc-och25E0vHRkPJKKdTuVAD0MiGc_Ttx=Q@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 329 bytes --]
Sorry, I messed subject in my previous two emails :( so I am sending it
again.
I have completed a draft proposal for this project. I will appreciate Jan,
Martin, or anybody else feedback on the same.
Here is the link to my proposal
https://docs.google.com/document/d/1r9kzsU96kOYfIhWZx62jx4ALG-J_aJs5U0sDpwFUtts/edit?usp=sharing
reply other threads:[~2023-04-04 0:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CA+1a67PX3TKHXJryc-och25E0vHRkPJKKdTuVAD0MiGc_Ttx=Q@mail.gmail.com' \
--to=rishiraj45035@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--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).