Date: Sat, 2 Jan 1999 22:58:30 -0500 (EST)
From: Daniel Reed <djr AT narnia DOT n DOT ml DOT org>
To: djgpp AT delorie DOT com
Subject: Re: parsing text to code
In-Reply-To: <001101be3389$c5fed160$dafde59b@djarrett.nwga.com>
Message-ID: <Pine.LNX.4.05.9901022248321.8870-100000@narnia.n.ml.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com

On Tue, 29 Dec 1998, David Jarrett wrote:
) >Anyone knows where i can find some understandable information about how
) >compilers work? Generally i want to implement a (very small) language of my
) >own, but i never studied compiler construction.
) You do understand that writing a compiler means that you know machine
) language? Im not talkin about assembly, but MACHINE code :)
Well, actually, the GNU C Compiler distribution is just made up of cc1
(the actual compiler--the program that translates C source code into
assembler) and gcc (the front end--the program that uses the compiler, the
assembler, and the linker to produce a binary)*. as (the assembler) and ld
(the linker) are both distributed in the GNU binutils distribution, not
with GCC at all.

* Actually GCC includes gcc, cc1, cc1plus (C++ compiler), cc1obj 
  (Objective C compiler), libgcc (the base set of GCC functions), and
  other misc. utilities.

-- 
Daniel Reed <n AT ml DOT org>
If Barbie is so popular, why do you have to buy her friends?