You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are some builds of solc that produce subtly different bytecode depending on the platform they are running on.
When running under the production build profile, we should force compilation through the wasm version of solc to isolate us from the underlying platform.
The text was updated successfully, but these errors were encountered:
In the light of #6336, this might not always be possible.
In particular, the solcjs-wrapper stores the compiler output from solcjs as a string, and so does our solcjs-runner. For very large codebases, the string containing the compiler output might exceed the maximum string length.
There are some builds of solc that produce subtly different bytecode depending on the platform they are running on.
When running under the production build profile, we should force compilation through the wasm version of solc to isolate us from the underlying platform.
The text was updated successfully, but these errors were encountered: