public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Peter Lafreniere <peter@n8pjl.ca>
To: GCC <gcc@gcc.gnu.org>
Cc: Peter Lafreniere <peter@n8pjl.ca>, "jh@suse.cz" <jh@suse.cz>
Subject: [GSoC] Introduction and query on LTO object emmission project
Date: Fri, 24 Feb 2023 16:02:11 +0000	[thread overview]
Message-ID: <Y2fYUPcdSb9I1jsxgvY7M9YPYgTeWkTe3JS4Mx1BHjwCaP6_jrFK6afYNdVad80y6wpCVkvepjsZiKeGtEZktwiES1KXR6queMgqNHNea3k=@n8pjl.ca> (raw)

Hi! I've been interested in compiler development for a while, and would love to
work with any of you as part of GSoC, or even just as a side-project on my own.

I'm an 18 year-old student going into university next year with a passion for all
things open source and low level. I consider myself fluent in c, and proficient
with c++, rust, and x86 assembly, but unfamiliar with practical compiler design.
I have done some reading on the theoretical aspects of compilers, however.

While I haven't worked with the GCC community before, I have worked with the linux
community and have made several small patches there, so I am familiar with both
email-based workflows and the principles of open-source development. 

This summer, I'm looking for more experience working on larger projects, as well
as getting into real compilers.

Of particular interest to me is the project idea labelled "Bypass assembler when
generating LTO object files." I see that the project was taken last year, but
I can find no sign of any changes committed to trunk 
(`git shortlog --after=2022-01-01 | grep -i -E "lto|assembl(er|y)"` shows nothing
related to this project) and no sign of any needed change made in the code.
Is this project still available?

I'm also willing to work on other projects, ideally in the middle/backend, but
currently I have only been experimenting with the gcc/[lto,data]-streamer* files.
If anyone has a small or medium sized project idea, please feel free to let me know.


I look forward to working with all of you in the future,

Peter Lafreniere
<peter@n8pjl.ca>


             reply	other threads:[~2023-02-24 16:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-24 16:02 Peter Lafreniere [this message]
2023-03-03 18:28 ` Jan Hubicka
2023-03-06 16:48   ` David Malcolm

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='Y2fYUPcdSb9I1jsxgvY7M9YPYgTeWkTe3JS4Mx1BHjwCaP6_jrFK6afYNdVad80y6wpCVkvepjsZiKeGtEZktwiES1KXR6queMgqNHNea3k=@n8pjl.ca' \
    --to=peter@n8pjl.ca \
    --cc=gcc@gcc.gnu.org \
    --cc=jh@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).