From: Tejas Joshi <tejasjoshi9673@gmail.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Martin Jambor <mjambor@suse.cz>, "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Further for GSoC.
Date: Wed, 07 Mar 2018 13:55:00 -0000 [thread overview]
Message-ID: <CACMrGjCqkk4FWyYahetuPLd5c8ZFw-W-SSyB-Sa+_AqawbOuDQ@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdRbjT6859BUpve8_0pzYcZZfYO=RifVHcUFvD7MjMSHBg@mail.gmail.com>
On 6 March 2018 at 22:25, Martin Jambor wrote:
> > You might have figured this out already but just in case something is
> > not clear:
> >
> > 1. How to check out our sources using svn and git is described at
> > https://gcc.gnu.org/svn.html and https://gcc.gnu.org/wiki/GitMirror
> > respectively, and
> >
> > 2. perhaps more importantly, how to configure, build and test GCC is
> > described in steps linked from https://gcc.gnu.org/install/ (look
> > for --disable-bootstrap, among other things).
>
> Or start with at https://gcc.gnu.org/wiki/InstallingGCC and
>
>> https://gcc.gnu.org/wiki/GettingStarted
>
> You need to check out the GCC source code from version control and find
the files and functions referenced in there (locating pieces of GCC code
using find, grep, etc. on the GCC source tree is something you'll need to
do a lot), and make sure you can build GCC, run the testsuite, save
results from a testsuite run, build and run the testsuite and compare the
results of the two runs (this is something that would need doing very many
times in the course of any project working on GCC).
Thank you all of you for your suggestions.
Was not mailing for some days because caught up in exams.
Interested in this project and working on it.
Thank you.
-Tejas
On 7 March 2018 at 18:05, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> On 6 March 2018 at 22:25, Martin Jambor wrote:
> > You might have figured this out already but just in case something is
> > not clear:
> >
> > 1. How to check out our sources using svn and git is described at
> > https://gcc.gnu.org/svn.html and https://gcc.gnu.org/wiki/GitMirror
> > respectively, and
> >
> > 2. perhaps more importantly, how to configure, build and test GCC is
> > described in steps linked from https://gcc.gnu.org/install/ (look
> > for --disable-bootstrap, among other things).
>
> Or start with at https://gcc.gnu.org/wiki/InstallingGCC and
> https://gcc.gnu.org/wiki/GettingStarted
>
prev parent reply other threads:[~2018-03-07 13:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 12:49 Tejas Joshi
2018-03-02 17:46 ` Joseph Myers
2018-03-06 22:25 ` Martin Jambor
2018-03-07 12:35 ` Jonathan Wakely
2018-03-07 13:55 ` Tejas Joshi [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=CACMrGjCqkk4FWyYahetuPLd5c8ZFw-W-SSyB-Sa+_AqawbOuDQ@mail.gmail.com \
--to=tejasjoshi9673@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--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).