Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Opcode "Loop" is not permitted in intializer expressions.'
See original GitHub issueIf I try to compile: https://aois.blob.core.windows.net/public/secp256k1.wasm
I get Opcode "Loop" is not permitted in intializer expressions.' when attempting to load.
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Opcode "Loop" is not permitted in intializer expressions
So my ultimate goal is to compile a C project into WASM, then convert the WASM to IL. (.NET Core) I was able...
Read more >c - For loop says expression syntax error when initializing ...
You are simply not allowed to declare variables elsewhere in a function, including in the initialization part of a for statement.
Read more >RealView Compilation Tools Errors and Warnings Reference ...
this operator is not allowed in a preprocessing expression ... <entity>, declared in for-loop initialization, may not be redeclared in this scope.
Read more >SyntaxError: a declaration in the head of a for-of loop can't ...
The head of a for...of loop contains an initializer expression. That is, a variable is declared and assigned a value for (const i...
Read more >The Optimizer — Solidity 0.8.21 documentation
It is not applied to loop iteration-condition, because the loop control flow does not allow this “outlining” of the inner expressions in all...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Unfortunately I don’t; the spare time I’ve spent on this project has been focused on making it able to run any WASM files that already work in browsers, not actually making new WASMs of my own. And there’s plenty of work left to do to get 100% of just that accomplished.
I do know that the WebAssembly working group is always looking to expand the capabilities, and it’s possible that initializer expressions with loops are legal in a prototype version of the spec. If you haven’t already, my instinct would be to ensure that a solid published-spec-ready compiler is used and not the latest beta/preview version.
Sure will do.