public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Martin Jambor <mjambor@suse.cz>
To: Tejas Joshi <tejasjoshi9673@gmail.com>
Cc: Joseph Myers <joseph@codesourcery.com>, gcc@gcc.gnu.org
Subject: Re: Further for GSoC.
Date: Tue, 06 Mar 2018 22:25:00 -0000	[thread overview]
Message-ID: <ri6y3j4eta5.fsf@suse.cz> (raw)
In-Reply-To: <alpine.DEB.2.20.1803021743380.29959@digraph.polyomino.org.uk>

Hello, Tejas,

On Fri, Mar 02 2018, Joseph Myers wrote:
> On Fri, 2 Mar 2018, Tejas Joshi wrote:
>
>> I have some university level experience of working and programming assembly
>> language under Intel 80386DX architecture. I think it may help for
>> implementing supports for other architectures. Just for start, you
>> mentioned roundeven function as a guide for start. Where can I find these
>> (e.g. real.c) .c files for detailed study of these functions so that I can
>> have broader scenario? I have GCC 7.2.0 installed and could not find it in
>> library nor in libc/.
>
> 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).
>

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).

If you have any specific question regarding any of these steps, feel
free to ask on the mailing list or the IRC.

Good luck,

Martin

  reply	other threads:[~2018-03-06 22:25 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 [this message]
2018-03-07 12:35     ` Jonathan Wakely
2018-03-07 13:55       ` Tejas Joshi

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=ri6y3j4eta5.fsf@suse.cz \
    --to=mjambor@suse.cz \
    --cc=gcc@gcc.gnu.org \
    --cc=joseph@codesourcery.com \
    --cc=tejasjoshi9673@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).