Alex Beregszaszi

Appendix C of _Architecture Optimization Manual_ (http://www.intel.com/content/www/us/en/architecture-and-technology/64-ia-32-architectures-optimization-manual.html) where _cycles_ are called _latency_.

Per pp. C-2: > Latency — The number of clock cycles that are required for the execution core to complete the > execution of all of the μops that form...

There is a draft available here: https://gist.github.com/axic/5bf506728005864461454dd4d37a7f37

Thank you @bnjbvr. I am afraid we cannot introduce architecture dependent pricing at all.

I think for now we should just go for: have a version number in the namespace. A contract can import a single version of the namespace, i.e. all imports must...

My other uses for custom sections are not that much ewasm specific and would feel weird to have one very complicated ewasm-specific custom section with all these different features smacked...

This is a different kind of versioning thread. The relevant one for that is https://github.com/ethereum/EIPs/issues/154

> 2. Have a custom section with the version in it. This proposal could be extended to be a platform metadata section giving opportunity for storing more details.

At EthCC @pepyakin has explained a potential way they are solving this problem. @pepyakin can you explain your solution briefly here?

I'm not sure I understand. It is versioned and this version in the README is the version number.