[Oberon] RISC5

[eas lab]

]> So that porting to a different architecture, just means replacing the
]> pseudoCode byte sequence/S?

]Yes but you must do some homework first to understand how the compiler
]works and how the code generation works.

If you make an allegation/claim which I disagree with, I should not just refer
you to the 'bible'. I should address your claim, with my counter example/S.

Since my thread has been snipped, let me try to reconstruct my thinking:
any [non-real-time] task that V5 performs, can be performed by a system
which performs the sequence of V5 [from the small vocabulary of 16].
instructions, possibly indirectly by instructions of non-V5 hardware.
=========
It's astounding that NW manages with 16 instructions. I haven't yet analysed it.
When I built P-code uProcs for <PASCAL with only byte & byteArray
types, I needed more than 16 Pcodes.

What about a P-code interpreter for rPi? Instead of going via C:
it's so small, it can be assembled directly. [My first pCode VM:
Fairchild-F8 needed hex-byte-codeing!].

But having Oberon, without the ETHO-interface is of little value?

Since Peter Matthias' ALO port seems to allow dissambling ARM,
interesting new ideas for rPi pop up.

== Chris Glur.


On 4/23/14, Chris Burrows <chris at cfbsoftware.com> wrote:
>> -----Original Message-----
>> From: Nemo [mailto:cym224 at gmail.com]
>> Sent: Wednesday, 23 April 2014 7:12 AM
>> To: ETH Oberon and related systems
>> Subject: Re: [Oberon] RISC5
>>
>> [...]
>> > So that porting to a different architecture, just means replacing the
>> > pseudoCode byte sequence/S?
>>
>> Yes but you must do some homework first to understand how the compiler
> works
>> and how the code generation works.  I am not familiar with the Oberon
>> compiler and thus cannot give you detailed guidance.  The compiler is
>> discussed in Chapt 12 of the book.  I suggest reading that chapter before
>> looking at the compiler source.
>>
>
> Excellent advice! If you have any difficulty understanding Chapter 12 I
> recommend that you go back one step and download and read Wirth's Compiler
> Construction book and work through the exercises:
>
> http://www.inf.ethz.ch/personal/wirth/CompilerConstruction/index.html
>
> Regards,
> Chris
>
> Chris Burrows
> CFB Software
> http://www.astrobe.com
>
>
>
>
> --
> Oberon at lists.inf.ethz.ch mailing list for ETH Oberon and related systems
> https://lists.inf.ethz.ch/mailman/listinfo/oberon
>