@fredd : My pleasure to read Your comment. Well, step by step:
(#1) “dynamical addressing” : Tell the true, I was very close to put THIS key question for SW guys whois going to port Erlang, Python, ..., another interpreter / virtual machine OR 'just' libraries. How these clever guys will deliver enough 'RAM' for their SWs. So, thanks for You, at now I am sure we have the same 'challenge'.
(#2) “OS v.s. dynamic language” : At the beginning I have had a 'doubt': an OS or virtual machines for a nice language. BUT(!) day by day I realized: (a) at finally 'a language' wants a same environment like just an OS can deliver (memory/scheduling/IO...) (b) which language?! (c) I really want to try out myself to write an OS. ('sorry' about this).
(#3) “FPGA” : You, as a sw person win(!) an another language: VHDL. Welcome on the board 'de' Parallella.
(#4) “chunk” : I can accept that, You are thinking about chunk/slice. Well, I have not finalized low/high memory management system of OS4E. I agree (a main point), compiler should support 'us' its own way, but I do not want so much as You written at Your sample.
(#5) “core-private, read-only, core-to-core, message-passing...” : In my point of view these also the area of the OS not an 'in-compiled function' in an application. But I think, Your idea will work well too.
(#6) “DMA” : Should work 'without' CPU. This is why we call it DMA. - There was an another issue/topic, as I understand it, it talks about the 'remote SDRAM' access. 'Solution' is the DMA(!) -
(#7) “extended memory management” : It will bring not 'just' the 'transparency', but a very good opportunity for a flexible, 'all language' supported system. - It is necessary but not sufficient condition for a 'real' OS on Epiphany. - I think, we should share our results 'soon'.
Regards, Gabor