[coyotos-dev] Executable format for Coyotos

[Pierre THIERRY]

Scribit Jonathan S. Shapiro dies 08/03/2007 hora 23:51:
> I'm not sure whether you want the high-level answer or the low-level
> answer.

Both are welcome.

> At a high level, the answer is: you go to the zero space constructor
> (zsc) and ask it to fabricate a new, demand-allocated space full of
> zeros for you. You map this at any convenient location and write bytes
> to it.

Shouldn't mapping involve invoking a capability to a kernel implemented
object?

> > That should be quite easier than creating an ELF executable. This
> > would be useful at least when prototyping the compiler...
> Yes, though caution is in order: don't forget the need for debugging
> information!

Well, I wouldn't expect my prototype to output DWARF initially. Would it
be needed to settle for BitC-specific conventions for it? It seems some
languages have such conventions, like C, C++, Ada or FORTRAN...

Curiously,
Pierre
-- 
nowhere.man at levallois.eu.org
OpenPGP 0xD9D50D8A
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://www.coyotos.org/pipermail/coyotos-dev/attachments/20070309/af18b447/attachment.bin