You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note that the data pointer of the slice arg to f has a ? in it. It shouldn't, that arg is live across the call to g and the compiler puts it somewhere known.
Looks like the compiler is spilling the pointer to an autotmp, not the arg slot.
(It then also spills it to the arg slot at the start of the function, presumably to make tracebacks better? But that copy might be stale, which is probably why the ? is still there.)
What did you expect to see?
no question mark
What did you see instead?
a question mark
The text was updated successfully, but these errors were encountered:
This looks like a bug in the type given to slice pointers by expand_calls. The location of the stack slot has type *int, but the ssa Value has type *uint8. The compiler refuses to use a stack slot that isn't typed correctly.
Go version
tip
What operating system and processor architecture are you using (
go env
)?What did you do?
When run, it prints
Note that the data pointer of the slice arg to
f
has a?
in it. It shouldn't, that arg is live across the call tog
and the compiler puts it somewhere known.Looks like the compiler is spilling the pointer to an autotmp, not the arg slot.
(It then also spills it to the arg slot at the start of the function, presumably to make tracebacks better? But that copy might be stale, which is probably why the
?
is still there.)What did you expect to see?
no question mark
What did you see instead?
a question mark
The text was updated successfully, but these errors were encountered: