type runtime.funcval
22 uses
runtime (current package)
cgocall.go#L290: cbFV := funcval{uintptr(fn)}
debugcall.go#L117: newg := newproc1(*(**funcval)(unsafe.Pointer(&fn)), unsafe.Pointer(&args), int32(unsafe.Sizeof(args)), gp, callerpc)
debugcall.go#L229: dispatchFV := funcval{dispatch}
heapdump.go#L226: func dumpfinalizer(obj unsafe.Pointer, fn *funcval, fint *_type, ot *ptrtype) {
heapdump.go#L424: func finq_callback(fn *funcval, obj unsafe.Pointer, nret uintptr, fint *_type, ot *ptrtype) {
mfinal.go#L42: fn *funcval // function to call (may be a heap pointer)
mfinal.go#L77: func queuefinalizer(p unsafe.Pointer, fn *funcval, nret uintptr, fint *_type, ot *ptrtype) {
mfinal.go#L127: func iterate_finq(callback func(*funcval, unsafe.Pointer, uintptr, *_type, *ptrtype)) {
mfinal.go#L418: if !addfinalizer(e.data, (*funcval)(f.data), nret, fint, ot) {
mheap.go#L1774: fn *funcval // May be a heap pointer.
mheap.go#L1781: func addfinalizer(p unsafe.Pointer, f *funcval, nret uintptr, fint *_type, ot *ptrtype) bool {
panic.go#L223: func deferproc(siz int32, fn *funcval) { // arguments of fn follow fn
panic.go#L834: closure := *(**funcval)(unsafe.Pointer(d.varp - uintptr(closureOffset)))
proc.go#L3974: func newproc(siz int32, fn *funcval) {
proc.go#L3999: func newproc1(fn *funcval, argp unsafe.Pointer, narg int32, callergp *g, callerpc uintptr) *g {
runtime2.go#L198: type funcval struct {
runtime2.go#L917: fn *funcval // can be nil for open-coded defers
stack.go#L1093: func gostartcallfn(gobuf *gobuf, fv *funcval) {
stubs.go#L173: func jmpdefer(fv *funcval, argp uintptr)
traceback.go#L110: var ctxt *funcval // Context pointer for unstarted goroutines. See issue #25897.
traceback.go#L125: ctxt = (*funcval)(gp.sched.ctxt)
traceback.go#L586: func getArgInfo(frame *stkframe, f funcInfo, needArgMap bool, ctxt *funcval) (arglen uintptr, argmap *bitvector) {
 |
The pages are generated with Golds v0.3.2-preview. (GOOS=darwin GOARCH=amd64)
Golds is a Go 101 project developed by Tapir Liu.
PR and bug reports are welcome and can be submitted to the issue list.
Please follow @Go100and1 (reachable from the left QR code) to get the latest news of Golds. |