I was noodling about how to minimize the cost of crossing the CGO barrier from Go code into C code and back.
Then I thought, what if I look at this the other way around. Instead of teaching the Go compiler how to better run C code, what if a C compiler (e.g. clang) was taught to generate code that used the Go stack and calling conventions. Theoretically, the cc output "in Go convention" could be linked with Go code without paying the CGO penalty, no? How crazy is this? :) -- 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/028ecd62-5f9f-4cb6-95df-a0b48ff3d825n%40googlegroups.com.
