public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Axel Kittenberger <Axel.Kittenberger@maxxio.at>
To: mike stump <mrs@windriver.com>,
	gcc@gcc.gnu.org, pinkfloydhomer@yahoo.com
Subject: Re: How to understand gcc
Date: Tue, 18 Dec 2001 02:59:00 -0000	[thread overview]
Message-ID: <200112180940.KAA01078@merlin.gams.co.at> (raw)
In-Reply-To: <200112172321.PAA11826@kankakee.wrs.com>

On Tuesday 18 December 2001 00:21, mike stump wrote:
> I think you can get answers as varied as people are.  I'll just toss
> out a few quick things that can keep you busy for 5 years learning.
>
> > From: "David Rasmussen" <pinkfloydhomer@yahoo.com>
> > To: <gcc@gcc.gnu.org>
> > Date: Mon, 17 Dec 2001 23:51:19 +0100
> >
> > How can I learn how gcc works?
> >
> :-)  I like simple, to the point questions that have simple answers.
>
> Unfortunately, yours is not.
>
> > I have taken one compiler course at my university,
>
> Good first step.  In addition, you can take advanced algorithms
> classes, theory classes...  You can also go to the library and find
> books on compilers and languages and read them all.
>
> > and I own the "Dragon book"
>
> I'd recommend reading and understanding it, if you haven't yet.  :-)
>
> > But really, I would like to have some sort of general understanding
> > about the design of gcc,
>
> You didn't mention if you had read the gcc manual, see our web site,
> under documentation, and manual.  If you have not, you should.  After
> that, please read the comments in the code, after that please read the
> code.  After that, try fixing 100 bugs or doing a port.  Your
> understanding will improve when trying to fix bugs or while doing a
> port.
>
> Also helpful, write an interpreter and compiler from the ground up.
>
> Lather, rinse, repeat.

Well that much of an arcane art how some people view compiler aren't the 
translors. And even worse some people working in that field like to be viewed 
as arcane wizards.  It's generally not true. Just take a look at the code an 
enjoy it. Never forget to read books/texts, but don't listen to people who 
require you to read a library before they even want to hear your thougths, 
(or want to let you fix 100 bugs, some are enough :o)) in science more than 
once an outsider moved the field on. And if you are more expirienced do not 
push the same acrcane attitude on newcomers.  

( However I do not view myself understand a lot or even some of it, but 
reading some texts in the past I often wondered why they ie. often use terms 
like "first class entities" without explaining what it means. 

My view is that some things as simple as they are like to be viewed 
complicated by the author or more expirienced users. )

  parent reply	other threads:[~2001-12-18  9:41 UTC|newest]

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

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=200112180940.KAA01078@merlin.gams.co.at \
    --to=axel.kittenberger@maxxio.at \
    --cc=gcc@gcc.gnu.org \
    --cc=mrs@windriver.com \
    --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).