Use static chain and libffi for Go closures
Andreas Schwab
schwab@linux-m68k.org
Mon Jan 19 10:41:00 GMT 2015
Ian Lance Taylor <iant@golang.org> writes:
> @@ -83,7 +83,7 @@
> #else /* !defined(USE_LIBFFI_CLOSURES) */
>
> void
> -makeFuncFFI(const struct __go_func_type *ftyp, ffi_go_closure *impl)
> +makeFuncFFI(const struct __go_func_type *ftyp, void *impl)
> {
> runtime_panicstring ("libgo built without FFI does not support "
> "reflect.MakeFunc");
../../../libgo/go/reflect/makefunc_ffi_c.c: In function âmakeFuncFFIâ:
../../../libgo/go/reflect/makefunc_ffi_c.c:86:42: error: unused parameter âftypâ [-Werror=unused-parameter]
makeFuncFFI(const struct __go_func_type *ftyp, void *impl)
^
../../../libgo/go/reflect/makefunc_ffi_c.c:86:54: error: unused parameter âimplâ [-Werror=unused-parameter]
makeFuncFFI(const struct __go_func_type *ftyp, void *impl)
^
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
More information about the Gcc-patches
mailing list