public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: shreya pohekar <shreyapohekar@gmail.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Interested to contribute in gsoc project
Date: Mon, 05 Mar 2018 15:31:00 -0000	[thread overview]
Message-ID: <CAFiYyc3jGe=M+vQucPmdzcPn6GxUy-qz0w=KAupabwHBqdMKVg@mail.gmail.com> (raw)
In-Reply-To: <5a9c48cf.d0c0620a.72855.7f85@mx.google.com>

On Sun, Mar 4, 2018 at 8:28 PM, shreya pohekar <shreyapohekar@gmail.com> wrote:
>
> Hello ,
> I am Shreya Pohekar, 2nd year student of University Institute of Technology ,RGPV ,Bhopal, India. I am interested in applying in GSoC 2018, and would like to contribute to the project : Parallelize the compilation using threads.
>
> I am working with c/c++ for a long time and would be an appropriate candidate for this project. I have worked a bit on GCC as well , when I was learning ARM exploitation.
>
> Can you guide me from where to get started? Or anything additional that I need to study.

A good starting point is the GCC WIKI at https://gcc.gnu.org/wiki - there's a
Getting Started with GCC Development section.  It's good to get one
self familiar
with building GCC from source and to see how to do edit/compile/debug cycles.

For the project in question you need to make yourself familiar with
the highlevel
compilation flow.  toplev.c is where the main controlling pieces stick together.
See do_compile -> compile_file -> symtab->finalize_compulation_unit -> compile
which will eventually lead to the "pass manager".  The ultimate task would be
to change the "pass manager" to execute chunks of passes in parallel and the
first hurdle is to identify chunks that can be executed in parallel without too
many changes (read: least global shared state).

Richard.


> Thanks
>
> Regards,
> Shreya
> Sent from Mail for Windows 10
>

  reply	other threads:[~2018-03-05 15:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-04 19:28 shreya pohekar
2018-03-05 15:31 ` Richard Biener [this message]
2018-03-06  4:57   ` shreya pohekar

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='CAFiYyc3jGe=M+vQucPmdzcPn6GxUy-qz0w=KAupabwHBqdMKVg@mail.gmail.com' \
    --to=richard.guenther@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=shreyapohekar@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).