4976b58ab1
The idea here is that there are two ways we can reference a function at runtime:
* Through a direct call, i.e. where the function is comptime-known
* Through a function pointer
This means we can easily perform a form of rudimentary escape analysis
on functions. If we ever see a `decl_ref` or `ref` of a function, we
have a function pointer, which could "leak" into runtime code, so we
emit the function; but for a plain `decl_val`, there's no need to.
This change means that `comptime { _ = f; }` no longer forces a function
to be emitted, which was used for some things (mainly tests). These use
sites have been replaced with `_ = &f;`, which still triggers analysis
of the function body, since you're taking a pointer to the function.
Resolves: #6256
Resolves: #15353
14 lines
241 B
Zig
14 lines
241 B
Zig
const A = struct { a: ?[1]i32 };
|
|
fn entry(a: *addrspace(.gs) [1]A) *addrspace(.gs) i32 {
|
|
return &a[0].a.?[0];
|
|
}
|
|
pub fn main() void {
|
|
_ = &entry;
|
|
}
|
|
|
|
// compile
|
|
// output_mode=Exe
|
|
// backend=llvm
|
|
// target=x86_64-linux,x86_64-macos
|
|
//
|