[coyotos-dev] Executable format for Coyotos

[Pierre THIERRY]

Scribit Jonathan S. Shapiro dies 04/03/2007 hora 20:56:
> For a self-hosted build, you would now run an additional tool. This
> tool extracts the loadable sections from the executable file and
> copies them into their proper positions into a new address space. This
> address space is what gets installed into the constructor (i.e. not
> the executable).

OK.

Now, my problem is, I'm pretty sure I don't quite get the big picture
about how memory objects are dealt with in Coyotos. Specifically, how
could an address space be built?

I didn't find in the Coyotos specification which interface should be
used for that purpose... Would an address space be built by asking the
space bank for the creation of a GPT and various pages?

> I think what you are missing is that address spaces are persistent, so
> there is no reason to do this step every time a program is started.

It's absolutely fantastic what persistence will make easily possible, it
seems, but that's a model I wasn't used to at all...

> You could also emit code directly into a target address space.

That should be quite easier than creating an ELF executable. This would
be useful at least when prototyping the compiler...

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/20070308/325f6c99/attachment.bin