For the record, I could do what I needed using the `//go:linkname`
directive.
My instrumentation tool injects statements that need features from another
package that I cannot import. So I forward declare functions using a given
link name that is implemented in another package - similarly to wha
I saw `go tool cover` does it, but I don't see anything else but a simple
call to printer.Fprint(w, f.fset, f.astFile) at
https://github.com/golang/tools/blob/master/cmd/cover/cover.go#L384
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To uns
is twice slower. So it may be a very
good solution for a first linux-only version, as I don't need return probes
(uretprobes seem to be a problem with Go's dynamic stack management).
--
Julio Guerra
--
You received this message because you are subscribed to the Google Groups
"go
and it doesn't use any plugin interface :(
--
Julio Guerra
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups
y the best option for performance and to avoid code
relocation at run time... Unfortunately, the go toolchain currently doesn't
have any "plugin" interface to add extra compilation stages.
--
Julio Guerra
--
You received this message because you are subscribed to the Google Groups
