Isn't it that C static function is only visible to the same file? The C code and Go code are not in the same file after code generation. Did I miss something?

static is only visible to the same "compilation unit", but everything in the cgo preamble is in the same compilation unit as the Go code.

(In the example above, you can invoke C.print_hello() directly from Go.)

Ok. I thought they are in different compilation units... Thanks.

static is only visible to the same "compilation unit", but everything in the cgo preamble is in the same compilation unit as the Go code.

(In the example above, you can invoke C.print_hello() directly from Go.)

@bcmills Looking at the cgo intermediate outputs @cherrymui might be right, the Go code is not in the same compilation unit as the static function. In the example above C.print_hello() can be invoked directly because that call does not point directly to the static function defined in the preamble but to a trampoline autogenerated by cgo that is not static and is defined in the same file as the static one (main.cgo2.c), therefore exported by the object file.

This is how main.cgo2.c looks like:

...
static void print_hello() { ... }
...

CGO_NO_SANITIZE_THREAD
void
_cgo_66eac9955d07_Cfunc_print_hello(void *v)
{
  struct {
    char unused;
  } __attribute__((__packed__, __gcc_struct__)) *_cgo_a = v;
  _cgo_tsan_acquire();
  print_hello();
  _cgo_tsan_release();
}

And this is the go wrapper in _cgo_gotypes.go:

//go:cgo_unsafe_args
func _Cfunc_f1() (r1 _Ctype_void) {
  _cgo_runtime_cgocall(_cgo_66eac9955d07_Cfunc_f1, uintptr(unsafe.Pointer(&r1)))
  ...
}

This does not happen when taking the address of a C function because the non-static trampoline is not used and C.print_hello points directly to the static function, therefore producing the linker error.

Taking as background my last comment, this issue could be fixed by:

• Create trampoline functions for all static C functions that are either directly invoked (current behavior) or whose address is retrieved (new addition).
• When the address of a static C function is retrieved return the address of the non-static trampoline function instead of the original static function.

This approach has the disadvantage that the address retrieved in Go will be different from the address retrieved in C, but I can't think on any other easy way to solve this issue.