[M3commit] [M3devel] CVS Update: cm3
Daniel Alejandro Benavides D.
dabenavidesd at yahoo.es
Wed Dec 23 05:47:27 CET 2009
Hi again:
I recall to have said about a virtualization infrastructure future framework for CM3 reusing existing work made by DEC and SPIN, if we manage to get the system running as a separate process in a given processor we will be definitely getting source code level compability between UNIX implementations by means of a huge historical system like DEC UNIX and a good balance on terms of security in the Modula-3 runtime protection of foreign code.
If there is no case of having user level DEC Unix server running in a host processor we can still emulate like they did and/or have a M3 Unix server inside the kernel like they planed to do.
In perspective SPINE (spin development) developed a embedded system in NT kernel without touching host system processor but the actual network interface card internal processor featuring several M3 applications running on it.
This would be a potential place for higher optimization in the CM3 system as we wouldn't have the usual architecture M3 guest-per system but a M3 host per system given the opportunities for it
Hope this helps in something, thanks in advance
--- El mar, 22/12/09, Daniel Alejandro Benavides D. <dabenavidesd at yahoo.es> escribió:
> De: Daniel Alejandro Benavides D. <dabenavidesd at yahoo.es>
> Asunto: Re: [M3devel] [M3commit] CVS Update: cm3
> Para: m3commit at elegosoft.com, jkrell at elego.de
> CC: m3devel at elegosoft.com
> Fecha: martes, 22 de diciembre, 2009 22:42
> Hi all:
> forgive my ignorance about the actual changes going on
> below copied M3commit message of Monday, December 21,
> 16:00:40 but what is this to have gcc code inside the
> compiler libs, I recommend to check the strict rules about
> this before performing such changes, Is there any problem
> getting gcc code inside the runtime libraries, even if this
> only used in level C code, this gets more C dependences in
> non-M3 code we are not able to guarantee, better UNSAFE than
> totally unmarked unsafe again. If this is not the case, and
> just a piece of m3cc related code I don't disqualify it
> yet.
> Thanks in advance
>
> --- El lun, 21/12/09, Jay Krell <jkrell at elego.de>
> escribió:
>
> > De: Jay Krell <jkrell at elego.de>
> > Asunto: [M3commit] CVS Update: cm3
> > Para: m3commit at elegosoft.com
> > Fecha: lunes, 21 de diciembre, 2009 11:00
> > CVSROOT: /usr/cvs
> > Changes by:
> > jkrell at birch. 09/12/21 16:00:40
> >
> > Modified files:
> >
> cm3/m3-libs/m3core/src/Csupport/libgcc/:
> > libgcc.c
> >
> > cm3/m3-libs/m3core/src/runtime/ALPHA_OSF/: RTStackC.c
>
> >
> cm3/m3-libs/m3core/src/runtime/DS3100/:
> > RTStackC.c
> >
> cm3/m3-libs/m3core/src/runtime/POSIX/:
> > RTOSbrk.c RTOSmmap.c
> >
> cm3/m3-libs/m3core/src/runtime/SOLgnu/:
> > RTStackC.c
> >
> cm3/m3-libs/m3core/src/runtime/SOLsun/:
> > RTStackC.c
> >
> cm3/m3-libs/m3core/src/runtime/WIN32/:
> > RTOSc.c
> >
> > cm3/m3-libs/m3core/src/runtime/ex_frame/: RTStackC.c
> >
> > Log message:
> > add mising #ifdef cplusplus
> extern "C" {
> > }
> >
> >
>
>
>
>
More information about the M3commit
mailing list