From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21372 invoked by alias); 18 Dec 2001 09:41:40 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 20884 invoked from network); 18 Dec 2001 09:40:20 -0000 Received: from unknown (HELO mario.gams.at) (194.42.96.10) by sources.redhat.com with SMTP; 18 Dec 2001 09:40:20 -0000 Received: from merlin.gams.co.at (IDENT:root@[193.46.232.13]) by mario.gams.at (8.9.3/8.9.3) with ESMTP id KAA12746; Tue, 18 Dec 2001 10:40:16 +0100 Received: from there (IDENT:axk@donald.maxxio.at [192.168.222.109]) by merlin.gams.co.at (8.9.3/8.9.3) with SMTP id KAA01078; Tue, 18 Dec 2001 10:40:16 +0100 Message-Id: <200112180940.KAA01078@merlin.gams.co.at> Content-Type: text/plain; charset="iso-8859-1" From: Axel Kittenberger Organization: Maxxio Technologies To: mike stump , gcc@gcc.gnu.org, pinkfloydhomer@yahoo.com Subject: Re: How to understand gcc Date: Tue, 18 Dec 2001 02:59:00 -0000 X-Mailer: KMail [version 1.3.2] References: <200112172321.PAA11826@kankakee.wrs.com> In-Reply-To: <200112172321.PAA11826@kankakee.wrs.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SW-Source: 2001-12/txt/msg00979.txt.bz2 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" > > To: > > 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. )