On Fri, Jul 15, 2011 at 05:15:35PM +0200, tlaro...@polynum.com wrote:
>[...]
> Writing down an explanation about the differences between the on file
> saved version, and the runtime structures, I wrote that portable was for
> sharing between whatever CPU architectures, while the in memory was
> fitting a particular architecture because the memory is tightly coupled
> to the cores and not shar... Oups! Hence the question.
Thinking about it a little more, whether the whole process memory is
migrated, that is not only "data" but instructions; in this case, the
new CPU processing has to understand the whole (natively or by
emulation) and in this case the program can "ignore" what's going on.
Or if the data is separated and shared, it has to be made "portable", by
whatever mean but known to the programmer and/or to the binary tools.
Well, I don't know if this is totally or only partially stupid. But this
was just an "en passant" question. Sorry for the noise. Back to work...
--
Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
