-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get richards.js running #204
Comments
Great example ty, will look at fixing soon |
Fixed 🎉 but there is another error for that file now 😅 making this a meta issue |
with this, richards.js no longer produces malformed Wasm (#204) test262: 50.14% (-0.01) | 🧪 48381 | 🤠 24260 (-1) | ❌ 6952 (+1) | 💀 15572 (-1) | 🏗️ 152 | 💥 331 | ⏰ 136 (+1) | 📝 978
Update: it no longer fails to compile 🎉 however, it still errors at runtime. There are a few bugs here, looking to get a minimal version working. |
Got the benchmark itself running but the harness still has issues, WIP |
Nice, good progress. Let me know once things are ready to try. Excited! |
lets richards.js go further without erroring (#204) test262: 50.14% | 🧪 48381 | 🤠 24260 | ❌ 6952 | 💀 15572 | 🏗️ 152 | 💥 331 | ⏰ 136 | 📝 978
I was trying to benchmark porffor and I got this issue when trying to compile the
richards.js
file:richards.js
The text was updated successfully, but these errors were encountered: