-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Slicing plus pointer decay segfaults the compiler #4423
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
Labels
Milestone
Comments
Looks like yet another result location bug. You can work around like this: const x = buf[0..:0];
foo(x); |
Indeed, the problem seems to be the cast from slice to pointer that generates a |
I think master is now correct. If someone else can eyeball and confirm, I'll add the following tests: compiler-errorexport fn foo() void {
var buf: [16]u8 = undefined;
const p: [*:0]const u8 = buf[0..:0];
}
behaviourexport fn foo() void {
var buf: [16]u8 = undefined;
const p: [*:0]const u8 = buf[0..15 :0];
} |
Vexu
added a commit
to Vexu/zig
that referenced
this issue
Dec 31, 2022
Closes ziglang#4144 Closes ziglang#4255 Closes ziglang#4372 Closes ziglang#4375 Closes ziglang#4380 Closes ziglang#4417 Closes ziglang#4423 Closes ziglang#4476 Closes ziglang#4528 Closes ziglang#4562 Closes ziglang#4572 Closes ziglang#4597 Closes ziglang#4639 Closes ziglang#4672 Closes ziglang#4782 Closes ziglang#4955 Closes ziglang#4984 Closes ziglang#4997 Closes ziglang#5010 Closes ziglang#5114 Closes ziglang#5166 Closes ziglang#5173 Closes ziglang#5276
Vexu
added a commit
to Vexu/zig
that referenced
this issue
Dec 31, 2022
Closes ziglang#4144 Closes ziglang#4255 Closes ziglang#4372 Closes ziglang#4375 Closes ziglang#4380 Closes ziglang#4417 Closes ziglang#4423 Closes ziglang#4476 Closes ziglang#4528 Closes ziglang#4562 Closes ziglang#4572 Closes ziglang#4597 Closes ziglang#4639 Closes ziglang#4672 Closes ziglang#4782 Closes ziglang#4955 Closes ziglang#4984 Closes ziglang#4997 Closes ziglang#5010 Closes ziglang#5114 Closes ziglang#5166 Closes ziglang#5173 Closes ziglang#5276
TUSF
pushed a commit
to TUSF/zig
that referenced
this issue
May 9, 2024
Closes ziglang#4144 Closes ziglang#4255 Closes ziglang#4372 Closes ziglang#4375 Closes ziglang#4380 Closes ziglang#4417 Closes ziglang#4423 Closes ziglang#4476 Closes ziglang#4528 Closes ziglang#4562 Closes ziglang#4572 Closes ziglang#4597 Closes ziglang#4639 Closes ziglang#4672 Closes ziglang#4782 Closes ziglang#4955 Closes ziglang#4984 Closes ziglang#4997 Closes ziglang#5010 Closes ziglang#5114 Closes ziglang#5166 Closes ziglang#5173 Closes ziglang#5276
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I wonder if I'm doing something wrong or (and that's very likely) it's just another bug.
The text was updated successfully, but these errors were encountered: