From: David Malcolm <dmalcolm@redhat.com>
To: Jan Hubicka <hubicka@ucw.cz>, Peter Lafreniere <peter@n8pjl.ca>
Cc: GCC <gcc@gcc.gnu.org>
Subject: Re: [GSoC] Introduction and query on LTO object emmission project
Date: Mon, 06 Mar 2023 11:48:14 -0500 [thread overview]
Message-ID: <59e73dc35716cd1e966a83bcdffdbc4ccebf8ab2.camel@redhat.com> (raw)
In-Reply-To: <ZAI8XIwfaGgbl8iJ@kam.mff.cuni.cz>
On Fri, 2023-03-03 at 19:28 +0100, Jan Hubicka via Gcc wrote:
> Hello,
> > 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.
Hi Peter
BTW, in case you haven't seen it, I've written a guide aimed at new GCC
contributors here:
https://gcc-newbies-guide.readthedocs.io/en/latest/index.html
A good first step would be to try to build gcc from source, add try
adding a simple warning that emits:
"hello world, I'm compiling function 'foo'"
for each function being compiled, and compile something with that...
then try stepping through cc1 doing that in the debugger. There are
instructions about that in the guide above.
Hope this is helpful
Dave
prev parent reply other threads:[~2023-03-06 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 16:02 Peter Lafreniere
2023-03-03 18:28 ` Jan Hubicka
2023-03-06 16:48 ` David Malcolm [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=59e73dc35716cd1e966a83bcdffdbc4ccebf8ab2.camel@redhat.com \
--to=dmalcolm@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=peter@n8pjl.ca \
/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).