public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Neil Booth <neil@daikokuya.demon.co.uk>
To: David Rasmussen <pinkfloydhomer@yahoo.com>
Cc: gcc@gcc.gnu.org
Subject: Re: How to understand gcc
Date: Mon, 17 Dec 2001 15:05:00 -0000	[thread overview]
Message-ID: <20011217230146.B27232@daikokuya.demon.co.uk> (raw)
In-Reply-To: <00dd01c1874d$58213f50$d26afea9@AMADEUS2>

David Rasmussen wrote:-

> Hi there,
> 
> How can I learn how gcc works? I have taken one compiler course at my
> university, and I own the "Dragon book" and Modern Compiler Implementation
> in ML. I am specifically interested in the C++ part of the compiler. But
> really, I would like to have some sort of general understanding about the
> design of gcc, how it is modularized, what techniques are used and which are
> not (i.e. design choices) etc. I can imagine that this is a near impossible
> task, but I want to know anyway :) I think it would be great if there was
> some sort of documentation that described the design and techniques of gcc.
> Ultimately, I would like to read a compiler text book, that used gcc as an
> example throughout.

From my experience (I knew nothing about compilers or GCC 2 yrs ago)
the best way is just to dive in and fix something, even if it's not
something you originally wanted to know about.  There's a GCC
beginner's project list (some of which are definitely non-trivial)
when you click "Projects" on the home page.  You could also try
picking easy-looking C++ bugs from GNATS and trying to fix them;
some hints on how you might do this are also on the beginner's page
I referred to.

The GCC documentation isn't bad either, and is getting better with
time.  It covers some of the internals, albeit sketchily and with many
out-of-date bits.

Good luck!

Neil.

  reply	other threads:[~2001-12-17 23:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-17 15:01 David Rasmussen
2001-12-17 15:05 ` Neil Booth [this message]
2001-12-17 15:46 mike stump
2001-12-17 16:20 ` David Rasmussen
2001-12-18  2:59 ` Axel Kittenberger
2001-12-18 15:03   ` Toon Moene
2001-12-18 15:39     ` Neil Booth
2001-12-18 23:27     ` Axel Kittenberger
2001-12-18 17:32 mike stump

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=20011217230146.B27232@daikokuya.demon.co.uk \
    --to=neil@daikokuya.demon.co.uk \
    --cc=gcc@gcc.gnu.org \
    --cc=pinkfloydhomer@yahoo.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).