public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: dewar@gnat.com (Robert Dewar)
To: Trevor.Jenkins@suneidesis.com, gcc@gcc.gnu.org
Subject: Re: Algol front end
Date: Tue, 14 May 2002 07:53:00 -0000	[thread overview]
Message-ID: <20020514135015.BE273F28D1@nile.gnat.com> (raw)

> I believe that the amount of work needed to put either of them within the
> gcc framework is about the same. a68g has a transput implementation closer
> to that of the Revised Report on Algol68. ctrans uses the underlying C
> printf function. Neither implemented the book paradigm or formatted
> output, which is rather like having a C compiler without any printf
> functions or varargs. The parser would need to be interfaced to the new
> tree; something that is going to hamper attempts to bring gpc into the
> fold. Sothis is clearly not soemthing that will make 3.2.

I am amazed that anyone would even consider that this could "make 3.2".
There is a *lot* of work here. Ctrans is a starting point, but only that.
My students this last semester have been working on Algol-68S implementations
in the compiler class (the assignment was to write in Algol-68S, and generate
code for MMIX, and do a full bootstrap -- at least two students already
succeeded in completing the bootstrap :-)

Anyway, that's why I know quite a bit about Ctrans, since quite a few students
used Ctrans as the path to the bootstrap.

             reply	other threads:[~2002-05-14 13:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-14  7:53 Robert Dewar [this message]
2002-05-14 11:15 ` Trevor Jenkins
  -- strict thread matches above, loose matches on Subject: below --
2002-05-09 13:44 Algol Front End Gaius Mulley
2002-05-08 12:15 Algol Front end Robert Dewar
2002-05-08 11:47 Arthur I Schwarz
2002-05-08  1:36 BCD [was Re: Algol front end] Bonzini Paolo
2002-05-14  2:52 ` Algol front end Lars Brinkhoff
2002-05-14  7:02   ` Trevor Jenkins
2002-05-07 20:12 Algol Front End Robert Dewar
2002-05-07 19:53 Algol Front end Robert Dewar
2002-05-07 16:45 Arthur I Schwarz
2002-05-07 15:15 Robert Dewar
2002-05-07  4:47 Robert Dewar
2002-05-07 13:43 ` Tim Josling
2002-05-07  4:29 Tim Josling
2002-05-06 18:14 Algol Front End Robert Dewar
2002-05-07  6:57 ` Jose E. Marchesi
2002-05-06 16:54 Tony Stratton
2002-05-06 19:23 ` Scott Robert Ladd
2002-05-07  0:47   ` Steven Bosscher
2002-05-07  7:02 ` Paul Koning

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=20020514135015.BE273F28D1@nile.gnat.com \
    --to=dewar@gnat.com \
    --cc=Trevor.Jenkins@suneidesis.com \
    --cc=gcc@gcc.gnu.org \
    /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).