Skip to content
This repository has been archived by the owner on Jan 5, 2019. It is now read-only.

javascript vs c++ #295

Open
cdetrio opened this issue Jul 26, 2018 · 1 comment
Open

javascript vs c++ #295

cdetrio opened this issue Jul 26, 2018 · 1 comment

Comments

@cdetrio
Copy link
Collaborator

cdetrio commented Jul 26, 2018

evm2wasm is made up of two modules: generateInterface.js and index.js. The interface generator generates a library of wast files ("interface wast files", with each wast file corresponds to an EVM opcode, for example). Index.js contains the run-time logic, which takes as input some EVM bytecode and transpiles it to ewasm bytecode using the library of interface wast files.

generateInterface.js can remain written in javascript. There is no rationale for porting it to a different language since it is only a build step, and not used during run-time.

index.js is being ported to c++, as the file evm2wasm.cpp. The rationale for porting it to C++ is that it can then be compiled to wasm, and then used as a system contract by any ewasm client.

@lrettig
Copy link
Member

lrettig commented Jul 26, 2018

So the action items here are:

  1. Get the cpp implementation up to scratch
  2. Deprecate/remove the javascript version of index.js

?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants