Thank you. I found that the best way (or only?) is to have an assembly function reference a Go function, then the compiler creates a wrapper that can be used.
On Tue, Nov 8, 2022 at 7:14 PM Ian Lance Taylor <i...@golang.org> wrote: > On Tue, Nov 8, 2022 at 7:55 AM Aviram Hassan <aviramyhas...@gmail.com> > wrote: > > > > I see that some runtime functions have both `abi0` interface and > `ABIInternal`. > > I was wondering what makes the compiler do so, and if I can make it do > the same for my defined functions? > > A bit of a background - I'm doing a bit of a lowlevel fun, and I want to > hook Go functions using just Go code (no assembly) so I want to have the > same interface as the original ones. > > There is background information for this at > > https://go.googlesource.com/proposal/+/refs/heads/master/design/27539-internal-abi.md > . > > Ian > -- 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.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CALOd%2BB2HXmMc%2BExPPGtBqzeHDPoBQ8mE1AUPZs6SaaySvdgN9A%40mail.gmail.com.
