From: robin@ruffnready.co.uk (Robin Birch)
Subject: [pups] lcc (was: GCC)
Date: Sun, 20 Jan 2002 10:52:38 +0000 [thread overview]
Message-ID: <woNqxNB2FqS8EwcB@falstaf.demon.co.uk> (raw)
In-Reply-To: <20020119112351.F60575@wantadilla.lemis.com>
In message <20020119112351.F60575 at wantadilla.lemis.com>, Greg Lehey
<grog at lemis.com> writes
>On Friday, 18 January 2002 at 17:13:26 -0500, norman at nose.cs.utoronto.ca wrote:
>> Jonathan Engdahl:
>>
>> Consider lcc, the Princeton C compiler. It's much smaller than gcc,
>>and ANSI
>> compliant.
>>
Where can it be found and is it legal to use it on the sorts of systems
that we play with?.
regards
Robin
>> lcc's a good compiler; it has become cc in my own peculiar Ancient UNIX
>> environment.
>
>It also has the advantage that there's a good book about it describing
>exactly how it works: "A retargetable C compiler: Design and
>implementation" by Christopher Fraser and David Hanson
>(Benjamin/Cummings, 1995, ISBN 0-8053-1670-1).
>
>Greg
>--
>Finger grog at lemis.com for PGP public key
>See complete headers for address and phone numbers
>_______________________________________________
>PUPS mailing list
>PUPS at minnie.tuhs.org
>http://minnie.tuhs.org/mailman/listinfo/pups
next prev parent reply other threads:[~2002-01-20 10:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-18 22:13 [pups] Re: GCC norman
2002-01-19 0:53 ` [pups] lcc (was: GCC) Greg Lehey
2002-01-20 10:52 ` Robin Birch [this message]
2002-01-20 14:38 ` emanuel stiebler
2002-01-20 15:47 ` Bill Gunshannon
2002-01-20 16:07 ` emanuel stiebler
2002-01-21 0:24 ` Greg Lehey
2002-05-10 4:43 ` Cyrille Lefevre
2002-05-10 5:08 ` Greg 'groggy' Lehey
2002-01-21 2:22 ` Jonathan Engdahl
2002-01-20 15:24 norman
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=woNqxNB2FqS8EwcB@falstaf.demon.co.uk \
--to=robin@ruffnready.co.uk \
/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 NNTP newsgroup(s).