On Thu, Aug 25, 2011 at 3:21 PM, Ligon Liu <[email protected]> wrote:
> can we get the statistical information on the server about the most > common execution trace of the JS, analyze it and just transmit the top > a few possible binaries to "computer B"? so it will be likely to > receive the binaries needed from cloud (and fallback to local JIT when > type prediction miss) > The binary image contains references to data outside of that image. Those addresses _will not_ map 1:1 on the remote site. As Jakob said, "no, not possible." > yeah, I agree transmitting binary code is dangerous -- but verifying > it is in fact easy, just deploy the JS-to-binary in trustable machine > and also check CRC32 will ensure the code's integrity? Is it still too > costly? > Sure, you can make sure the image itself transfers, but that does you no good. How are you going to re-map the pointers which that data uses? If you just drop in the remote-compiled image, it's going to reference addresses which _certainly_ do not point to the proper memory in the local process. That problem is not solvable in the generic case (but it might be using an engine specifically designed for that purpose. v8 is not such an engine.). As Jakob said, "no, not possible." -- ----- stephan beal http://wanderinghorse.net/home/stephan/ -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users
