Re: Current state of the `ooc' project?

[jnzimmer@informatik.uni-kl.de]

Mike wrote:
> That should get me to the point where I have a working Oberon-2 compiler
> on the BeBox.  The next stages will then be to add this back-end to OOC.
> I'm still kind of waiting as well for someone else to develop an interface
> between the GSA tree and a typical code generator.

Is the ETH Oberon-2 compiler OP2 based? If yes, you surely cannot
reuse its PPC back-end for OOC, as they are based on different
abstraction levels. OP2's internal structure reflects most of the
Oberon-2 constructs while OOC is nearly assembler.
  The main task for an OP2 back-end is to translate Oberon-2
statements to machine code patterns, for an OOC back-end to map GSA
data and control flow onto machine level data and control flow.
  Btw, what exactly is a `typical code generator'? A `typical code
generator' for OOC should be one which translates GSA to machine
code...

  Juergen