From: "Rupert Wood" <me@rupey.net>
To: "'Danish Samad'" <danishsamad@yahoo.com>
Cc: <gcc-help@gcc.gnu.org>
Subject: RE: help wanted
Date: Wed, 10 Oct 2001 23:44:00 -0000 [thread overview]
Message-ID: <616BE6A276E3714788D2AC35C40CD18D03A936@whale.softwire.co.uk> (raw)
In-Reply-To: <20011011050609.67746.qmail@web20109.mail.yahoo.com>
Danish Samad wrote:
> The GCC project I have downloaded is huge containing a lot of other
> compilers, assemblers etc. Can you please guide me where to find the
> gcc c compilers front end with documentation.
There's plenty of it, yes, but if you're going to attempt some heavy
backend wizardry then you will have to get your head around most of it
sooner or later.
Unless you have a merged gcc-binutils tree (not likely if you downloaded
it yourself) then you don't actually have any assemblers bundled.
Instead, you have
/ Top level makefiles for cygnus toolchain
/gcc C front end and generic backend
/gcc/config CPU/OS specific instruction sets and ABIs
/gcc/cp C++ front end
/gcc/objc Objective-C front end
/gcc/f Fortran front end
/gcc/java Java front end
/gcc/po Internationalization 'pot' translation files
/gcc/intl Internationalization library
/gcc/fixinc Fixes for non-standards-conformant system headers
/gcc/doc Documentation
/gcc/ginclude GCC build includes
/gcc/testsuite GCC regression testsuite
etc. plus a number of runtime libraries and helper libraries (libiberty)
at the top level.
i.e. you'll find the C-front end and the generic backend in the gcc
directory, plus you'll need one of the machine description files (.md)
plus a number of headers and source files in the config tree to tell the
generic backend how to generate processor specific code.
All documentation is build with GCC into at least .info format. It is
also available online at http://gcc.gnu.org/onlinedocs/
Good luck!
Rup.
next prev parent reply other threads:[~2001-10-10 23:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-10 22:06 Danish Samad
2001-10-10 23:44 ` Rupert Wood [this message]
2002-08-12 8:22 rojesh p
2003-03-17 16:44 Help wanted Jane Liang
2003-03-17 16:53 ` Ben Davis
2003-03-17 19:16 Jane Liang
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=616BE6A276E3714788D2AC35C40CD18D03A936@whale.softwire.co.uk \
--to=me@rupey.net \
--cc=danishsamad@yahoo.com \
--cc=gcc-help@gcc.gnu.org \
/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).