-
-
Notifications
You must be signed in to change notification settings - Fork 313
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
Zig 0.11 llvm 16 #5851
Zig 0.11 llvm 16 #5851
Conversation
4105c81
to
baad74f
Compare
ad89aec
to
5b63276
Compare
e59d9b6
to
ae9fc9b
Compare
It looks like for |
Also, quite confused why after my pr we are still failing to run zig 0.11.0. It is still trying to build zig in ci with 0.9.1 |
Non-nix workflows on self-hosted servers have zig 0.9.1 installed, I'll install zig 0.11.0 on there and try to use our ROC_ZIG env var. |
For the nix issues I'm going to upgrade to rust 1.72.0 but on main branch first, so we know that's not causing any issues here. |
🙏 Thanks so much. Definitely will be helpful to keep that complexity out of this PR. |
228dd1a
to
a26247d
Compare
Awesome, so it looks like nix with rust 1.71.0 is new enough. No need to update to 1.72.0 for this branch!!! |
Zig changed the way to build wasm-modules. Before 0.11 the wasm-module exported all exported symbols. Starting from 0.11, you have to do it explicitly with Maybe this is relevant for this PR? If not, then sorry for the noise. (I am exited about this PR. Thank you for your work ❤️). |
@folkertdev and @brian-carroll, not sure if either of you will have time or energy to look at the issues on this branch, but I think that you two are probably the most knowledgable in fixing the issues we are hitting. So any support would be greatly appreciated. Landing this will be awesome. Also, I am a bit confused why more wasm tests are failing now. Apparently updating rust or some other change broke more of the wasm tests. That or maybe I screw up at some point and reverted a wasm based change, not fully sure. (could be something else that was pulled in when rebasing on main) EDIT: Also @Anton-4, thanks for pulling out the specific issues. |
@bhansconnect I'll pull the branch and have a quick look! I don't have a lot of free time this week unfortunately but might have a bit more from next week or the week after. |
I fixed the issues with the llvm wasm backend. Also #5859 seems to be fixed now (at least those tests all succeed for me locally) |
c0fc321
to
31e88e5
Compare
My current plan is to try and fix any dev wasm related issues but then submit these changes even if it leaves windows abi stuff slightly more broken. I want to make larger changes to how we call bitcode functions in a separate PR. That will resolve the windows abi issues. I don't want to block this on that work. |
088a83b
to
0cb2aea
Compare
So did some more local testing, most of the wasm failures where caused by the update from rust With rust er...kinda. It seems that no mater the rust version, all of these failures happen on my x86 linux machine, but my m1 mac follows the version related failure change that I mentioned above. It is super strange to me. |
0cb2aea
to
42d148d
Compare
The CI failure is a segfault but it only happens outside of nix, so I'm wondering if it's some kind of dependency issue. I'm investigating. |
I have one more thing I'm going to try out tomorrow and if that does not work I'll do a clean OS install on that CI machine. |
I think the 2 cli run tests that are failing in |
I failed to reproduce as well, the failures do indeed happen every time. I'm going to compare binaries on CI vs a very similar environment and see if I can learn anything from that. |
This does look like a real bug, not just mixed dependencies.
An interesting failure of building with
I compared I've created an archive with the executables, asm, and strings output: |
I'm going to take a stab at upgrading the debugir repo to llvm 16. |
see #5904 Signed-off-by: Anton-4 <[email protected]>
226cfa0
to
0f5b112
Compare
Signed-off-by: Anton-4 <[email protected]>
Signed-off-by: Anton-4 <[email protected]>
I updated zig with homebrew, which I expect will result in the least problems Signed-off-by: Anton-4 <[email protected]>
Nightlies are good 🎉 |
woooooooooo!!!! 😍 😍 😍 😍 😍 amazing work landing this!!! |
This branch isn't quite ready, but I want to see what we get out of CI. Currently, I think that only a few gen_dev (I think a lambdaset issue leading to invalid frees) and gen_wasm (not sure, but probably linking related) tests are failing. Hopefully we can patch those up and get this submitted soon.
Also, no idea the state of windows, but hopeful it isn't too bad.