-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Compiler crash after new comptime-mutable memory analysis merge #19457
Comments
Regressed by #19414. |
I don't get a compiler crash, I get a build script error:
Looks like I need some kind of SDK in order to reproduce. |
@andrewrk Yeah that's a separate issue: you need Xcode installed with both the macOS and iOS SDKs (check to download in GUI). You can probably just disable iOS too with some changes to make that a bit easier on yourself. |
FYI I built Zig from source but due to other breaking changes the branch isn't building for other reasons now. I'm working on getting the deps updated so I can get back to the reported issue and verify it again. |
With the latest Zig I now only get this:
I believe this is already being tracked, so once this gets fixed up then I'll try again. cc @mlugg |
Should be handled by my latest PR - it's not passing CI yet, but it can build ghostty in my testing. If you're able to build a compiler, would you be able to check it works for you? |
@mlugg with your PR:
|
I got that past that with @mlugg's PR. I believe this issue is resolved when that is merged. |
Fix landed in 1fb2381. |
Zig Version
0.12.0-dev.3457+341857e5c
Steps to Reproduce and Observed Behavior
Check out this branch: https://github.com/mitchellh/ghostty/tree/update-zig (all Zig core has access to this repo, if you don't ping me)
Run
zig build test
orzig build
. This crash only happens on macOS.I don't have a debug build of the compiler to get the error, sorry.
Expected Behavior
No crash, though I do expect that that branch at the time of authoring this issue has more comptime var violations I have to fix.
The text was updated successfully, but these errors were encountered: